- 
    Enhancement 
- 
    Resolution: Fixed
- 
     P2 P2
- 
    None
- 
        b60
- 
        Verified
| Issue | Fix Version | Assignee | Priority | Status | Resolution | Resolved In Build | 
|---|---|---|---|---|---|---|
| JDK-8084652 | emb-9 | Weijun Wang | P2 | Resolved | Fixed | team | 
LoginContext needs to be re-examined to see how it will work with module boundaries. It currently uses Core Reflection to invoke the handler/callback and this will require adjustments to work for the case that the handler is itself in a named module.
Here's an example error when running the JCK with a prototype build:
<Server> Authentication failed: unable to access LoginModule: Class javax.security.auth.login.LoginContext (module java.base) can not access a member of class com.sun.security.auth.module.Krb5LoginModule (module jdk.security.auth) with modifiers "public"
where the underlying error is an IllegalAccessException bring thrown by Class#newInstance because jdk.security.auth is not readable to java.base.
- backported by
- 
                    JDK-8084652 auth.login.LoginContext needs to be updated to work with modules -           
- Resolved
 
-         
- duplicates
- 
                    JDK-6562449 LoginContext does not all allow overloading of login method in LoginModule -           
- Closed
 
-         
- relates to
- 
                    JDK-8075804 Refactor LoginContext.invokePriv() -           
- Closed
 
-         
- 
                    JDK-8230297 Slow LoginContext.login() due to repeated ServiceLoader lookups -           
- Closed
 
-         
- 
                    JDK-8078813 Test JAAS with modules -           
- Resolved
 
-         
- 
                    JDK-8076035 Security Guide Updates for LoginModule loading change (JDK-8047789) -           
- Resolved
 
-         
             (1 relates to)
        
    
               There are no Sub-Tasks for this issue.