[
https://jira.duraspace.org/browse/DS-652?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=18396#action_18396
]
Flávio Botelho commented on DS-652:
-----------------------------------
This issue should be closed.
> Wrong behaviour of special groups at login. Use only special groups of the
> authetication that DID authenticate the user.
> ------------------------------------------------------------------------------------------------------------------------
>
> Key: DS-652
> URL: https://jira.duraspace.org/browse/DS-652
> Project: DSpace
> Issue Type: Bug
> Components: DSpace API
> Affects Versions: 1.6.0
> Reporter: Flávio Botelho
> Priority: Major
> Attachments: Fix_behaviour_of_autentication_specialGroups.patch
>
>
> We have internal users autheticating thru LDAP. And external users are still
> able to create new users.
> Unfortunally the authentication is putting all external users created thru
> the Login Authentication also in the ldap.login.specialgroup, of course that
> is not expected.
> Looking at code at AuthenticationManager it becomes clear that it is adding
> ALL the special groups of ALL the possible authentication mechanism, which
> doesnt make any sense whatsoever...
> It should only add special groups of the authentication mechanism that DID
> authenticate the user.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://jira.duraspace.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
------------------------------------------------------------------------------
_______________________________________________
Dspace-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/dspace-devel
