Custom Authentication Provider Created Without Attributes When Using configToScript Command To Copy Recreate a Domain
(Doc ID 2174129.1)
Last updated on OCTOBER 02, 2023
Applies to:
Oracle WebLogic Server - Version 12.2.1.0.0 and laterInformation in this document applies to any platform.
Symptoms
By using configToScript command to recreate a domain, the newly created domain has all resources (JDBC, JMS, Default and Custom authentication providers, etc...) correctly created but there aren't properties set for the Custom Authentication Provider matching the original one.
Below steps were performed:
1. Run configToScript([configPath], [pyPath], [overwrite], [propertiesFile], [createDeploymentScript]) as configToScript('<dir>/<DomainName>', '<dir>//wlst_scripts/config.py', 'true', '<dir>/config.properties', 'false')
2. Edit the created properties file to add the correct username, password, and domain directory.
3. Change the ports and managed server names in the config.py file.
4. Start the WLST tool.
5. Run the command execfile('<dir>/config.py')
6. After completion of the configuration, the newly created domain has JDBC resources, JMS resources and the default authentication providers. But custom authentication provider is getting created but with not the properties configuration as of the old domain.
2. Edit the created properties file to add the correct username, password, and domain directory.
3. Change the ports and managed server names in the config.py file.
4. Start the WLST tool.
5. Run the command execfile('<dir>/config.py')
6. After completion of the configuration, the newly created domain has JDBC resources, JMS resources and the default authentication providers. But custom authentication provider is getting created but with not the properties configuration as of the old domain.
Cause
To view full details, sign in with your My Oracle Support account. |
|
Don't have a My Oracle Support account? Click to get started! |
In this Document
| Symptoms |
| Cause |
| Solution |