chemistry-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Tahir Malik (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (CMIS-887) RunAs Authentication possiblity
Date Thu, 29 Jan 2015 12:40:34 GMT

    [ https://issues.apache.org/jira/browse/CMIS-887?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14296779#comment-14296779
] 

Tahir Malik commented on CMIS-887:
----------------------------------

Great thanks Sasha & Florian for the info.

I'll take a look at it, but I think there is still ways to improve it. I'm not sure how, but
this seems like something which every integration between systems has.
So I in this case have a custom external service to authenticate, Sasha has extended the TokenCallContextHandler
and you're suggesting to extend the Standard authentication provider.

And hence we probably get back that the CMIS spec needs to be changed :D. I'll file something
at OASIS so this gets some attention.

> RunAs Authentication possiblity
> -------------------------------
>
>                 Key: CMIS-887
>                 URL: https://issues.apache.org/jira/browse/CMIS-887
>             Project: Chemistry
>          Issue Type: Improvement
>          Components: opencmis-client, opencmis-server
>    Affects Versions: OpenCMIS 0.12.0
>         Environment: Alfresco 4.2
>            Reporter: Tahir Malik
>
> There is no possibility to define a RunAs user through CMIS.
> At the moment we have a custom webscript in Alfresco which logs in as the RunAs user
and returns the ticket.
> Then we use the ticket in the password field and do our stuff.
> It would be nice to extent the Authentication mechanism to supply extra parameters and
control them server side so this is not needed.
> If this is already possible, then I didn't knew that and I'd love to have some info how
to do that.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Mime
View raw message