[KNOX-2390] Configure SAML using provider parameters

• Type: Task
• Status: Resolved
• Priority: Major
• Resolution: Fixed
• Affects Version/s: 1.4.0
• Fix Version/s: 1.5.0
• Component/s: Server
• Assignee: Sandor Molnar
• Reporter: Sandor Molnar
• Created: 16/Jun/20 09:37
• Updated: 19/Jun/20 07:55
• Resolved: 19/Jun/20 07:55

Description

Currently, there is a bunch of SAML parameters which the Pac4j federation provider knows about and can be used to update SAML 2 configuration:

• saml.keystorePassword
• saml.privateKeyPassword
• saml.keystorePath
• saml.keystoreAlias
• saml.identityProviderMetadataPath
• saml.maximumAuthenticationLifetime
• saml.serviceProviderEntityId
• saml.serviceProviderMetadataPath
• saml.destinationBindingType

However, there are other SAML 2 configurations that also should be configurable via provider parameters. For instance: the default value of useNameQualifier changed from 'false' to 'true' in pac4j v3.7.0 (and changed back to 'false' in v3.8.2) which may cause an issue with ADFS integration.

The purpose of this Jira is to identify a list of SAML 2 configuration that should be configurable and make it happen via the Pac4j federation provider parameters.

Issue Links

• links to: GitHub Pull Request #348