[OASIS Issue Tracker] (CMIS-777) Authentication in a Single Sign On (SSO) environment

[OASIS Issues Tracker <workgroup_mailer@lists.oasis-open.org>]

    [ https://issues.oasis-open.org/browse/CMIS-777?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=41751#comment-41751 ] 

Peter Monks commented on CMIS-777:
----------------------------------

One piece of feedback I've heard was that one of the challenges of authentication isn't so much that it's not standardised, but that there's no easy way for a client application to "discover" which authentication schemes a given CMIS server supports.  They noted that this is in contrast to CMIS capabilities, which are readily discoverable.

Perhaps in lieu of being able to standardise authentication itself, a standardised way for clients to discover which authentication scheme(s) a given CMIS server supports would be a reasonable compromise?

> Authentication in a Single Sign On (SSO) environment
> ----------------------------------------------------
>
>                 Key: CMIS-777
>                 URL: https://issues.oasis-open.org/browse/CMIS-777
>             Project: OASIS Content Management Interoperability Services (CMIS) TC
>          Issue Type: New Feature
>          Components: Domain Model
>    Affects Versions: Proposals for 2.0
>            Reporter: David Choy
>             Fix For: Proposals for 2.0
>
>
> Triggered by a 24 July 2014 public comment, this is created as a discussion forum on the subject of authentication in an SSO environment. Please feel free to inject your thoughts, experience, questions, suggestions, or any other comments that you may have. We want to collect all the inputs we can get and then assess if there is anything we can do.



--
This message was sent by Atlassian JIRA
(v6.2.2#6258)