[security-dev] Replacing Seam RunAsOperation (impersonate)
Pedro Igor Silva
psilva at redhat.com
Fri Jul 10 08:27:27 EDT 2015
You are right, PL is missing that feature. It was planned but now the PL and KC are merging I'm not sure if we are going to implement it in PL.
Regarding your question, there is no easy way to specify your own Identity implementation. However, I'm wondering if you can use a custom CDI scope for that. PicketLink allows you to define a specific scope for the Identity bean.
----- Original Message -----
From: "Sean Flanigan" <sflaniga at redhat.com>
To: security-dev at lists.jboss.org
Sent: Friday, July 10, 2015 5:37:51 AM
Subject: [security-dev] Replacing Seam RunAsOperation (impersonate)
I was hoping I had missed an impersonation feature, but now I'm
thinking there isn't one in PicketLink. Assuming I have to subclass and
@Specialize org.picketlink.internal.DefaultIdentity, how would I go
about convincing PicketLink to use my implementation?
org.picketlink.extension.PicketLinkExtension seems to be vetoing my
implementation. Is there some way of telling (or overriding)
IdentityBeanDefinition to use my Identity bean class?
Principal Software Engineer
Globalisation Tools Engineering
security-dev mailing list
security-dev at lists.jboss.org
More information about the security-dev