Cannot start weblogic after changing control flag

Question

I read the article at http://edocs.weblogicfans.net/wls/docs81/secmanage/providers.html#1187595
I create 2 SQLAuthenticators, MySQLAuthenticator and testSQLAuthenticator (Someone told me that it is not necessary to do that. But I just do a test). In my weblogic 10.3.5, it has 2 default authenticators, DefaultAuthenticator and DefaultIdentityAsserter.
1, MySQLAuthenticator=testSQLAuthenticator=DefaultAuthenticator=OPTIONAL, weblogic can be startup
2, MySQLAuthenticator=REQUISITE, testSQLAuthenticator=DefaultAuthenticator=OPTIONAL, weblogic cannot be startup
3, MySQLAuthenticator=SUFFICIENT, testSQLAuthenticator=DefaultAuthenticator=OPTIONAL, weblogic can be startup
4, MySQLAuthenticator=testSQLAuthenticator=SUFFICIENT, DefaultAuthenticator=OPTIONAL, weblogic can be startup
5, MySQLAuthenticator=testSQLAuthenticator=DefaultAuthenticator=SUFFICIENT, weblogic can be startup
6, MySQLAuthenticator=REQUIRED, testSQLAuthenticator=DefaultAuthenticator=SUFFICIENT, weblogic cannot be startup
7, MySQLAuthenticator=REQUIRED, testSQLAuthenticator=DefaultAuthenticator=OPTIONAL, weblogic cannot be startup
In the article: REQUISITE—If the user passes the authentication test of this Authentication provider, other providers are executed but can fail (except for Authentication providers with the JAAS Control Flag set to REQUIRED)
Why I cannot set REQUIRED and REQUISITE to authenticators. Where is wrong?

Answer 1

The control flags you are using mean the following:
- REQUIRED – the LoginModule is required to succeed.
If it succeeds or fails, authentication still continues to proceed down the LoginModule list.
- REQUISITE – the LoginModule is required to succeed.
If it succeeds, authentication continues down the LoginModule list.
If it fails, control immediately returns to the application (authentication does not proceed down the LoginModule list).
- SUFFICIENT – the LoginModule is not required to succeed.
If it does succeed, control immediately returns to the application (authentication does not proceed down the LoginModule list).
If it fails, authentication continues down the LoginModule list.
- OPTIONAL – the LoginModule is not required to succeed.
If it succeeds or fails, authentication still continues to proceed down the LoginModule list.
Note that the MySQLAuthenticator and the DefaultAuthenticator are LoginModule in JAAS terms.
When you take the second option from your post - MySQLAuthenticator=REQUISITE and DefaultAuthenticator=OPTIONAL.
In this case when you login into WebLogic by using the admin password, the login procedure goes through the MySQLAuthenticator
and checks if the admin username and password are present if not as is noted above the whole login fails as the loginmodule
is flagged as REQUISITE and you cannnot login.
The same applies when you set a control flag to REQUIRED it has to succeed otherwise the whole logiin does not succeed