[jboss-jira] [JBoss JIRA] Resolved: (SECURITY-132) Traditional Authentication

Darran Lofthouse (JIRA) jira-events at lists.jboss.org
Sat Nov 27 14:06:30 EST 2010


     [ https://jira.jboss.org/browse/SECURITY-132?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Darran Lofthouse resolved SECURITY-132.
---------------------------------------

    Resolution: Done


Added a usernamePasswordDomain option to the SPNEGOLoginModule to allow a domain to be specified that can be used to delegate username/password authentication to.

The reason for using delegation rather than chaining is so that this can delegate to a domain using a JDK supplied Kerberos Login module, this means that regardless of the mechanism used we will be able to use the Kerberos subject for further delegation later on.


> Traditional Authentication
> --------------------------
>
>                 Key: SECURITY-132
>                 URL: https://jira.jboss.org/browse/SECURITY-132
>             Project: PicketBox (JBoss Security and Identity Management)
>          Issue Type: Task
>      Security Level: Public(Everyone can see) 
>          Components: Negotiation
>            Reporter: Darran Lofthouse
>            Assignee: Darran Lofthouse
>             Fix For: Negotiation_2.0.4
>
>
> Incomming call may be traditional username / password type call but consideration needs to be given for potential outbound call.

-- 
This message is automatically generated by JIRA.
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

        


More information about the jboss-jira mailing list