[
https://issues.jboss.org/browse/ELY-835?page=com.atlassian.jira.plugin.sy...
]
Jan Kalina edited comment on ELY-835 at 1/20/17 5:10 PM:
---------------------------------------------------------
[~jmartisk] I dont think so - this only mean username will not be automatically searched
in all trusted domains of current domain.
*The inflow is already possible, it only have to be done explicitly* - if you have
obtained SecurityIdentity (admin) from trusted domain (ManagementDomain) and
SecurityDomain into which you would like to inflow (BatchDomain), you can obtain
SecurityIdentity of BachDomain from it.
Example in test:
https://github.com/wildfly-security/wildfly-elytron/blob/master/src/test/...
was (Author: honza889):
[~jmartisk] I dont think so - this only mean username will not be automatically searched
in all trusted domains of current domain.
The inflow is already possible, it only have to be done explicitly - if you have obtained
SecurityIdentity (admin) from trusted domain (ManagementDomain) and SecurityDomain into
which you would like to inflow (BatchDomain), you can obtain SecurityIdentity of
BachDomain from it.
As shown in test:
https://github.com/wildfly-security/wildfly-elytron/blob/master/src/test/...
SecurityIdentity Automatic Outflow
----------------------------------
Key: ELY-835
URL:
https://issues.jboss.org/browse/ELY-835
Project: WildFly Elytron
Issue Type: Enhancement
Components: API / SPI
Reporter: Darran Lofthouse
Assignee: Jan Kalina
Priority: Blocker
Fix For: 1.1.0.Beta21
We previously discussed that when runAs is called on a SecurityIdentity this should
pro-actively outflow to predefined security domains (which it has in
trusted-security-domains?) so it does not need to be manually inflowed at a later point.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)