[
https://issues.apache.org/jira/browse/JUDDI-187?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12671318#action_12671318
]
Kurt T Stam commented on JUDDI-187:
-----------------------------------
-UddiEntityPublisher no longer has persistent KeyGen collection
-Logic in UddiEntityPublisher changed to dynamically find a publisher's key
generators
-Detached the publisher reference from UddiEntity class, now this class simply
contains the non-nullable authorizedName
-Publisher keys no longer are required to be prefixed by the root partition,
they can provide their own domain key
-Authentication split into two phases: authenticate and identify
-Authenticators adjusted to account for new phases
-JUDDIAuthenticator is new default Authenticator, authenticates based on
Publisher entity
-Install process adjusted to account for above changes
-Tests and test files adjusted to account for above changes
> Updating AuthenticationTest and Adding documentation on the new
> Authentication Approach
> ---------------------------------------------------------------------------------------
>
> Key: JUDDI-187
> URL: https://issues.apache.org/jira/browse/JUDDI-187
> Project: jUDDI
> Issue Type: Task
> Affects Versions: 3.0alpha
> Reporter: Kurt T Stam
> Assignee: Jeff Faath
> Fix For: 3.0alpha
>
>
> By default, a user now equals a publisher. So requests will need to have a
> user, which is a publisher, that is in the publisher database. However, user
> can write their own Authentication implementation where they can decouple
> usernames from publisher, if you'd like to have multiple users who can
> publish into the UDDI for you publisher account.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
