Skip to content

Commit dfca285

Browse files
committed
added known limitations to the bottom of the security providers readme
1 parent 430d799 commit dfca285

File tree

1 file changed

+5
-1
lines changed

1 file changed

+5
-1
lines changed

site/security_providers.md

Lines changed: 5 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -97,7 +97,7 @@ topology:
9797

9898
Prior to using this tooling to create or update a domain with a custom security provider, there are several prerequisites. First, WebLogic Server requires the custom MBean JAR to be in the Oracle Home directory before it can be configured, WLSERVER/server/lib/mbeantypes. Second, WebLogic Scripting Tool, WLST, requires that the schema JAR be placed in the Oracle Home directory before WLST offline can be used to configure it, ORACLEHOME/oracle_common/lib/schematypes. Generating an MBean JAR documentation can be found in the WebLogic Server [documentation](https://docs.oracle.com/middleware/12213/wls/DEVSP/generate_mbeantype.htm#DEVSP617). Generating the schema JAR can be done with the prepareCustomProvider script provided in the WebLogic Server installation.
9999

100-
The format for a custom security provider is slightly different than for a built-in provider in that the custom provider must supply the class name of the provider in the model between the provider name and the attributes for the provider. In the custom `CredentialMapper` example below, note the location in the model of 'examples.security.providers.SampleCredentialMapper':
100+
The format for a custom security provider is slightly different than for a built-in provider in that the custom provider must supply the package name of the provider in the model between the provider name and the attributes for the provider. In the custom `CredentialMapper` example below, note the location in the model of 'examples.security.providers.SampleCredentialMapper':
101101

102102
```yaml
103103
CredentialMapper:
@@ -107,3 +107,7 @@ The format for a custom security provider is slightly different than for a built
107107
CredentialMappingDeploymentEnabled: true:
108108
```
109109

110+
#### Known Limitations
111+
112+
- `Adjudicator` provider types cannot be added or modified due to a limitation in WLST.
113+
- `PasswordCredentials` provider types cannot be updated in WLST online.

0 commit comments

Comments
 (0)