Users do not appear out of OID in weblogic

Question

I want to do SSO for webcenter
Do as it is written in Oracle ® Retail Accelerators Guide for WebCenter 11g.
You must add the OSSO Identity Asserter to a WebLogic domain. In addition to the
OSSO Identity Asserter, Oracle recommends the following Authentication providers:
DefaultAuthenticator
OID Authenticator
To add providers to your WebLogic domain for OSSO Identity Assertion:
1. Log on to the WebLogic Administration Console.
2. Under the Domain Structure (left navigation pane), click Security Realms. The
Summary of Security Realms screen appears.
3. On the Summary of Security Realms screen, click the default security realm
(myrealm). The Settings for myrealm screen appears.
4. On the Settings for myrealm screen, click the Providers tab, and then click New.
The Create a New Authentication Provider screen appears.
5. Enter a provider name for the OSSO Identity Asserter, select the relevant type, and
then click OK. For example:
Name: OSSO Identity Asserter
Type: OSSOIdentityAsserter
The new provider is added to the list of providers and appears on the Settings for
myrealm screen.
6. Click the name of the provider you just added.
7. On the Common tab, set the relevant values for the parameter, set the Control
Flag value to Sufficient, and then click Save.
8. On the Providers tab, click DefaultAuthenticator. The Settings for
DefaultAuthenticator screen appears.
9. Set the Control Flag value to Optional and click Save.
10. On the Providers tab, click New. The Create a New Authentication Provider
screen appears.
11. Enter a provider name for the OID Authenticator, select the relevant type, and
then click OK. For example:
Name: OID Authenticator
Type: OracleInternetDirectoryAuthenticator
The new provider is added to the list of providers and appears on the Settings for
myrealm screen.
12. Click the name of the provider you just added and review the settings. Do not
change the Control Flag value until you have verified that the Oracle Internet
Directory configuration is valid.
On the Provider Specific tab, specify relevant values in the following fields:
Host – specify the host name of the Oracle Internet Directory.
Port – specify the port number associated with the Oracle Internet Directory.
Principal – specify an LDAP administrative user. For example, cn=orcladmin.
Credential – specify the password associated with the LDAP administrative
user.
Confirm Credential – enter the password again to confirm the credential.
User Base DN – specify the distinguished name (DN) of the tree in the Oracle
Internet Directory that contains the users.
Use Retrieved User Name as Principal – select this check box.
Group Base DN – specify the distinguished name (DN) of the tree in the
Oracle Internet Directory that contains the groups.
Propagate Cause For Login Exception – select this check box.
14. Click Save.
The order in which providers populate a subject with principals is significant. You
may want to reorder the list of all providers in your realm and bring the newly
added provider to the top of the list, similar to the following:
OSSO Identity Asserter
OID Authenticator
Default Authenticator
Default Identity Asserter
16. Save all configuration settings and restart the WebLogic server for the changes to
take effect.
**17. Log on to the WebLogic Administration Console and navigate to the Settings for**
**myrealm screen.**
**18. Click the Users and Groups tab to view a list of users and groups included in the**
**configured Authentication providers. You should see user names from the Oracle**
**Internet Directory configuration, which verifies that the configuration is valid and**
**working.**
But I do not see the users who are registered in the OID
as you can see the logs as to why they do not appear?

Answer 1

I solved problem, but
When I change control flag to SUFFICIENT for OID Authentication Provider I can’t start weblogic.
./startWebLogic.sh
<Server subsystem failed. Reason: weblogic.security.SecurityInitializationException: User weblogic is not permitted to boot the server; The server policy may have changed in such a way that the user is no longer able to boot the server.Reboot the server with the administrative user account or contact the system administrator to update the server policy definitions.
weblogic.security.SecurityInitializationException: User weblogic is not permitted to boot the server; The server policy may have changed in such a way that the user is no longer able to boot the server.Reboot the server with the administrative user account or contact the system administrator to update the server policy definitions.
In OID is the user weblogic with the same password which in config file with login and password and group Administrators.