[
https://issues.apache.org/jira/browse/GUACAMOLE-103?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17144482#comment-17144482
]
Nick Couchman commented on GUACAMOLE-103:
-----------------------------------------
Presumably the "ACS URL" is different from the already-implement callback URL
parameter?
https://github.com/apache/guacamole-client/blob/181350160b1d3c0f55597c7b5e6d9d62e9c74e53/extensions/guacamole-auth-saml/src/main/java/org/apache/guacamole/auth/saml/conf/ConfigurationService.java#L337-L339
samlMap.put(SettingsBuilder.SP_ASSERTION_CONSUMER_SERVICE_URL_PROPERTY_KEY,
getCallbackUrl().toString() + "/api/ext/saml/callback");
??
> SAML 2.0 support for user authentication
> ----------------------------------------
>
> Key: GUACAMOLE-103
> URL: https://issues.apache.org/jira/browse/GUACAMOLE-103
> Project: Guacamole
> Issue Type: New Feature
> Reporter: Justin P
> Assignee: Nick Couchman
> Priority: Minor
> Fix For: 1.2.0
>
>
> It'd be great if Guacamole supported SAML 2.0 so it could integrate with an
> organization's single sign-on (SSO) solution (especially popular platforms
> like OneLogin, Okta, Bitium, etc.)
> This would make authenticating to Guacamole easier for an organization's
> users, and it would make organization's IT/IS admins happier being able to
> apply authentication security controls to guacamole, such as password
> complexity rules, two-factor authentication rules, etc.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
