[ https://issues.apache.org/jira/browse/ARGUS-29?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Velmurugan Periasamy updated ARGUS-29:
--------------------------------------
Attachment: 0001-ARGUS-29-Allow-Kerberized-Username-during-repo-creat.patch
> Unable to enter kerberized username during the repository creation
> ------------------------------------------------------------------
>
> Key: ARGUS-29
> URL: https://issues.apache.org/jira/browse/ARGUS-29
> Project: Argus
> Issue Type: Bug
> Reporter: Velmurugan Periasamy
> Attachments: 0001-ARGUS-29-Allow-Kerberized-Username-during-repo-creat.patch
>
>
> 1. For repository creation, the username is NOT accepting kerberozied user due to UI/Back-end
validations.
> a. UI is not allowing long usernames like (e.g.: policymgr/mypolicymanagerhost.myit.my-internal-domain.dom@KDC.DOMAIN.COM)
> b. UI is also validating this username when they try to do Test Connectivity.
> Fix:
> a. UI should remove all validation when accepting the username for repository.
> b. If a “/“ character is present in the username, the UI should use all string before
“/“ as the internal username for policy-creation and user creation in XA user (and portal
user table). For example, if the username is provided as policymgr/mypolicymanagerhost.myit.my-internal-domain.dom@KDC.DOMAIN.COM
then the UI should use policymgr as the username for creating default policies and to create
username in XA user/portal tables.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
|