[
https://issues.apache.org/jira/browse/CMIS-887?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14297432#comment-14297432
]
Florian Müller commented on CMIS-887:
-------------------------------------
For Alfresco you may want to look into [header based
authentication|http://wiki.alfresco.com/wiki/Alfresco_Authentication_Subsystems#Header_based_external_authentication].
If that fits your use case, you only need an authentictaion provider.
If you really need your own authentication mechanism on the server side, extend
the
[BasicAuthCallContextHandler|https://svn.apache.org/viewvc/chemistry/opencmis/trunk/chemistry-opencmis-server/chemistry-opencmis-server-bindings/src/main/java/org/apache/chemistry/opencmis/server/shared/BasicAuthCallContextHandler.java?view=markup].
Technically, the TokenCallContextHandler works too, but has been designed for
a different use case.
> 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)
