This is a sample configuration of the authenticators.xml. It contains a list of authenticator elements where each of them describes a different authenticator. Attribute "name" is a mandatory attr which is used to identify each of the authenticator. It is possible to disable an installed authenticator. The optional attribute "disabled" is used for that purpose and it defaults to 'false' if not mentioned specifically.
Each authenticator has a priority level, which is used in runtime to identify the authenticator with the highest priority which can handle a particular authentication request. 'Config' element is used for the authenticator specific configurations. These configurations are given as parameter elements. <Authenticators xmlns="http://wso2.org/projects/carbon/authenticators.xml";> <!-- Authenticator Configurations for TokenUIAuthenticator --> <Authenticator name="TokenUIAuthenticator" disabled="true"> <priority>5</priority> </Authenticator> <!-- Authenticator Configurations for SAML2SSOAuthenticator --> <Authenticator name="SAML2SSOAuthenticator"> <priority>10</priority> <config> <parameter name="LoginPage">/carbon/admin/login.jsp</parameter> <parameter name="ServiceProviderID">carbonServer</parameter> <parameter name="IdentityProviderSSOServiceURL"> https://localhost:9443/samlsso</parameter> </config> </Authenticator> </Authenticators> Please provide your feedback on this model. Thanks, Thilina On Fri, Apr 1, 2011 at 12:02 PM, Sameera Jayasoma <[email protected]> wrote: > > > On Fri, Apr 1, 2011 at 11:46 AM, Thilina Buddhika <[email protected]>wrote: > >> Hi Folks, >> >> At the moment, we have some configurations related to Carbon authenticator >> framework scattered across multiple configuration files. For instance, all >> the authenticator configurations and priorities are set in the carbon.xml >> and SSO configurations are in the user-mgt.xml. Also since users can write >> their own authenticators and plug into Carbon, we should provide a default >> place to put their configurations. >> >> After an offline discussion with Azeez, we thought of introducing a new >> config. file called 'authenticators.xml' which will be categorized as an >> advanced configuration file. Users have to modify it only if they want to >> use a different authentication mechanism other than the default >> authenticator. >> >> WDYT ? >> > > +1 for applying separation of concerns concept. Merging all authenticators > related configurations to a single config files is better approach. > > Sameera > >> >> Thanks, >> Thilina >> >> -- >> Thilina Buddhika >> Senior Software Engineer >> WSO2 Inc. ; http://wso2.com >> lean . enterprise . middleware >> >> phone : +94 77 44 88 727 >> blog : http://blog.thilinamb.com >> >> _______________________________________________ >> Carbon-dev mailing list >> [email protected] >> http://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev >> >> > > > -- > Sameera Jayasoma > Technical Lead and Product Manager, WSO2 Carbon > > WSO2, Inc. (http://wso2.com) > email: [email protected] > blog: http://tech.jayasoma.org > > Lean . Enterprise . Middleware > -- Thilina Buddhika Senior Software Engineer WSO2 Inc. ; http://wso2.com lean . enterprise . middleware phone : +94 77 44 88 727 blog : http://blog.thilinamb.com
_______________________________________________ Carbon-dev mailing list [email protected] http://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev
