<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>topic Re: How create my own authentication for acces to a page on Alfresco 5 in Alfresco Forum</title>
    <link>https://connect.hyland.com/t5/alfresco-forum/how-create-my-own-authentication-for-acces-to-a-page-on-alfresco/m-p/48840#M18945</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;There is no way to develop / add a custom "authentication family". The values for the authentication element are defined by an enum in Java code, and as such cannot be extended / added to without patching the corresponding classes of the Surf framework. Also bear in mind that the definition of authentication on the web script descriptor does not denote any special authentication method, but only the level of user that is allowed to access the page. If you need more fine grained access control, e.g. require a very specific set of permissions in the Repository backend, you can still do your custom check in your template / web script controller&amp;nbsp;JavaScript and stop / report back an unauthorised access if the user is not allowed to access the page. Alfresco already does the same thing for Sites, e.g. they check that in a controller script, not via authentication.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Thu, 06 Dec 2018 11:09:47 GMT</pubDate>
    <dc:creator>afaust</dc:creator>
    <dc:date>2018-12-06T11:09:47Z</dc:date>
    <item>
      <title>How create my own authentication for acces to a page on Alfresco 5</title>
      <link>https://connect.hyland.com/t5/alfresco-forum/how-create-my-own-authentication-for-acces-to-a-page-on-alfresco/m-p/48839#M18944</link>
      <description>Hi i want to make usable the "repository" page only for the member of my own customize authentication.Here my use case with the file i modified on the share webapp with my own extension module:// ============================// SHARE AMP//===============================//-----------------------------</description>
      <pubDate>Wed, 05 Dec 2018 13:39:57 GMT</pubDate>
      <guid>https://connect.hyland.com/t5/alfresco-forum/how-create-my-own-authentication-for-acces-to-a-page-on-alfresco/m-p/48839#M18944</guid>
      <dc:creator>AlfrescoZZZ</dc:creator>
      <dc:date>2018-12-05T13:39:57Z</dc:date>
    </item>
    <item>
      <title>Re: How create my own authentication for acces to a page on Alfresco 5</title>
      <link>https://connect.hyland.com/t5/alfresco-forum/how-create-my-own-authentication-for-acces-to-a-page-on-alfresco/m-p/48840#M18945</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;There is no way to develop / add a custom "authentication family". The values for the authentication element are defined by an enum in Java code, and as such cannot be extended / added to without patching the corresponding classes of the Surf framework. Also bear in mind that the definition of authentication on the web script descriptor does not denote any special authentication method, but only the level of user that is allowed to access the page. If you need more fine grained access control, e.g. require a very specific set of permissions in the Repository backend, you can still do your custom check in your template / web script controller&amp;nbsp;JavaScript and stop / report back an unauthorised access if the user is not allowed to access the page. Alfresco already does the same thing for Sites, e.g. they check that in a controller script, not via authentication.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 06 Dec 2018 11:09:47 GMT</pubDate>
      <guid>https://connect.hyland.com/t5/alfresco-forum/how-create-my-own-authentication-for-acces-to-a-page-on-alfresco/m-p/48840#M18945</guid>
      <dc:creator>afaust</dc:creator>
      <dc:date>2018-12-06T11:09:47Z</dc:date>
    </item>
  </channel>
</rss>

