1 Reply Latest reply on Jun 8, 2009 12:05 PM by Anil Saldanha

    SubjectSecurityManager 4.0.3 to 5.0.1 migration issue

    Ken Hohl Newbie

      I am porting from 4.0.3 to 5.0.1 a large EJB 2.0 application that is integrated with a legacy system and includes a custom security module. Some details about what I had to do to get this working initially are described in this post -


      The application does not build against 5.0.1 jars. I implement SubjectSecurityManager and RealmMapping and I'm getting an error that getTargetPrincipal(java.security.Principal,java.util.Map<java.lang.String,java.lang.Object>) must be implemented. Given this, I assume 5.0.1 is not fully backwards compatible and I must implement this new method. This disappoints me, but I guess I'll have to deal with it. Where can I find additional details about what I must do in this new method?

        • 1. Re: SubjectSecurityManager 4.0.3 to 5.0.1 migration issue
          Anil Saldanha Master

          JBoss4 to JBoss5 is a major upgrade. So we cannot always guarantee that methods will not be added or deprecated in JBoss interfaces, across major revisions.

          We make efforts to maintain backwards compatibility as much as possible.

          The getTargetPrincipal was mainly added to focus on identities across security domains such as federated domains. So it is only for special usage. You can just throw a RuntimeException if you want.