Help save net neutrality! Learn more.
Close

#662 XMLLoginConfig broken

v3.0 Rabbit Hole
closed-out-of-date
nobody
JBossSX (62)
5
2002-07-10
2002-07-10
No

in parseModule(), the logic to determine the flag is
broken, as the assumption that
javax.security.auth.login.AppConfigurationEntry.LoginMo
duleControlFlag.OPTIONAL.toString() returns "optional"
is false. It returns "LoginModuleControlFlag: optional"
and so on for REQUIRED, REQUISITE, and
SUFFICIENT. As XMLLoginConfig defaults the flag to
REQUIRED, the problem is masked. The workaround is
to specify the full text of "LoginModuleControlFlag: x" in
login-config.xml.

I have attached a version of XMLLoginConfig.java with
changes in parseModule to fix the bug. If the flag
specified isn't one of {required, requisite, sufficient,
optional}, I throw an Exception. I wasn't sure what
Exception class to use or what level of detail to put in
the message...

Discussion

  • Jonathan Leech

    Jonathan Leech - 2002-07-10

    XMLLoginConfig.java with modifications

     
  • Scott M Stark

    Scott M Stark - 2002-07-10

    Logged In: YES
    user_id=175228

    This has been fixed since 3.0.1RC1.

     
  • Scott M Stark

    Scott M Stark - 2002-07-10
    • status: open --> closed-out-of-date
     

Log in to post a comment.