[
https://issues.apache.org/jira/browse/OAK-8763?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16978588#comment-16978588
]
Angela Schreiber commented on OAK-8763:
---------------------------------------
[~baedke], i don't necessarily agree with your statement that the context
provider _messes up_ the subject upon login ;-) see also OAK-8710 for some
additional comments regarding reproducibility. having said that: see oak
documentation [0] and test cases with oak on how to create a
AccessControlContext that returns a read-only subject. you may also find a
prominent example within the AEM code base (service login).
[0]
http://jackrabbit.apache.org/oak/docs/security/authentication/preauthentication.html
> LoginContextProviderImpl uses any subject found in the AccessControlContext.
> ----------------------------------------------------------------------------
>
> Key: OAK-8763
> URL: https://issues.apache.org/jira/browse/OAK-8763
> Project: Jackrabbit Oak
> Issue Type: Bug
> Components: security-spi
> Reporter: Manfred Baedke
> Assignee: Angela Schreiber
> Priority: Major
> Attachments: OAK-8763.patch
>
>
> LoginContextProviderImpl#getLoginContext(...) extracts the most recent
> subject from the AccessControlContext and then uses it for either a
> PreAuthContext or a JaasLoginContext. This is wrong, because there is no
> reason to assume that such a subject has anything to do with Oak. It
> particularly hurts when it's readonly, because JAAS will then silently fail
> to add principals and credentials.
> We would need a way to identify pre-authenticated subjects and subjects that
> are not pre-authenticated should not be used to create a JaasLoginContext.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
