Manage security providers

Before you begin

The WebLogic Security Service supports a wide variety of security architectures, including multiple possible security providers.

Before you configure security providers for your WebLogic security realm, you should have a good understanding of how the WebLogic Security Service works and what sort of security architecture you want for your WebLogic environment. See:

Your security architecture can include the default security providers included in WebLogic Server, security providers developed by third parties, or custom security providers you develop yourself. Types of security providers include:

Authentication providers
identity assertion providers
Authorizaton providers
Adjudication providers
Role Mapping providers
credential mapping providers
Auditing providers

Note:

Once you have made a configuration change to a security provider, you cannot invoke management operations (such as configuring a user or a group) until you activate the configuration change and restart the server. You can override this limitation by enabling Allow Security Management Operations if Non-dynamic Changes have been Made on the Domain: Security: General page. Setting this attribute to true permits users to perform security management operations without restarting the server. This attribute is reset to false when a new console session begins.

The following topics describe how to configure and manage security providers. The steps you need to take depend on the security architecture you have decided to implement in your security realm.

Related Tasks

} } (document.images){ dcs_imgarray[dcs_ptr] = new Image; dcs_imgarray[dcs_ptr].src = dcs_src; WT[myMeta.name.substring(3)]=myMeta.content; } if DCSext[myMeta.name.substring(7)]=myMeta.content; } } } } for (N in DCS){P+=A( N, DCS[N]);} for (N in WT){P+=A( "WT."+N, WT[N]);} for (N in DCSext){P+=A( N, DCSext[N]);} //} aCrumb=aCookie[i].split("="); if (crumb==aCrumb[0]){ return aCrumb[1]; } } return null; } i=0;i