[
https://issues.apache.org/jira/browse/KNOX-659?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15123875#comment-15123875
]
Larry McCay commented on KNOX-659:
----------------------------------
In order to know whether or not to add the saml default params, we need to know
whether SAML is a desired pac4j client. Which creates a cumbersome
interrogation of the configured params. Instead, I have decided to make the
clientName param required for all pac4j topologies. In so doing, we can easily
check whether the SAML2Client is contained in the optionally comma separated
list of client names and know to add the defaults.
> Default Keystore Details in Pac4j Provider SAML Config to Gateway Identity
> --------------------------------------------------------------------------
>
> Key: KNOX-659
> URL: https://issues.apache.org/jira/browse/KNOX-659
> Project: Apache Knox
> Issue Type: Bug
> Components: Server
> Reporter: Larry McCay
> Assignee: Larry McCay
> Priority: Blocker
> Fix For: 0.8.0
>
>
> The need to configure the full path to the Knox gateway.jks and the
> corresponding passwords needs to be provided by default. This will remove the
> storage of passwords in clear text and improve usability/management.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
