Create Or Modify This RDBMS Security Store
/management/weblogic/{version}/edit/securityConfiguration/realms/{name}/RDBMSSecurityStore
Modify this RDBMS security store if it exists; otherwise, create it.
Request
- application/json
-
name: string
The name property of the instance in the collection.
-
version: string
The version of the WebLogic REST interface.
-
X-Requested-By: string
The 'X-Requested-By' header is used to protect against Cross-Site Request Forgery (CSRF) attacks. The value is an arbitrary name such as 'MyClient'.
Must contain the modified RDBMS security store model.
object
-
connectionProperties(optional):
string
The JDBC driver specific connection parameters. This attribute is a comma-delimited list of key-value properties to pass to the driver for configuration of JDBC connection pool, in the form of
xxKey=xxValue, xxKey=xxValue
The syntax of the attribute will be validated and an
InvalidAttributeValueException
is thrown if the check failed. -
connectionURL(optional):
string
The URL of the database to which to connect. The format of the URL varies by JDBC driver.
The URL is passed to the JDBC driver to create the physical database connections.
Constraints
- legal null
-
driverName(optional):
string
The full package name of the JDBC driver class used to create the physical database connections in the connection pool. Note that this driver class must be in the classpath of any server to which it is deployed.
For example:
oracle.jdbc.OracleDriver
com.microsoft.sqlserver.jdbc.SQLServerDriver
It must be the name of a class that implements the
java.sql.Driver
interface. The full pathname of the JDBC driver is available in the documentation.Constraints
- legal null
-
JMSExceptionReconnectAttempts(optional):
integer(int32)
Minimum Value:
0
Default Value:0
The number of times to attempt to reconnect if the JMS system notifies Kodo of a serious connection error.
The default is 0, and by default the error is logged but ignored. The value cannot be less than 0.
-
JMSTopic(optional):
string
The JMS topic to which the Kodo remote commit provider should publish notifications and subscribe for notifications sent from other JVMs. This setting varies depending on the application server in use.
-
JMSTopicConnectionFactory(optional):
string
The JNDI name of a
javax.jms.TopicConnectionFactory
instance to use for finding JMS topics.This setting varies depending on the application server in use. Consult the JMS documentation for details about how this parameter should be specified.
-
JNDIPassword(optional):
string(password)
The password to authenticate the user defined in the
JNDIUsername
attribute for Kodo notification.When getting the value of this attribute, WebLogic Server does the following:
Retrieves the value of the
JNDIPasswordEncrypted
attribute.Decrypts the value and returns the unencrypted password as a String.
When you set the value of this attribute, WebLogic Server does the following:
Encrypts the value.
Sets the value of the
JNDIPasswordEncrypted
attribute to the encrypted value.
Using this attribute (
JNDIPassword
) is a potential security risk because the String object (which contains the unencrypted password) remains in the JVM's memory until garbage collection removes it and the memory is reallocated. Depending on how memory is allocated in the JVM, a significant amount of time could pass before this unencrypted data is removed from memory.Instead of using this attribute, use
JNDIPasswordEncrypted
-
JNDIUsername(optional):
string
The JNDI user name used for Kodo notification.
-
name(optional):
string
Read Only:
true
Default Value:RDBMSSecurityStore
The name of this configuration.
-
notificationProperties(optional):
string
The comma-delimited list of key-value properties to pass to the JNDI InitialContext on construction, in the form of
xxKey=xxValue, xxKey=xxValue
The following are examples of keys:
java.naming.provider.url:
property for specifying configuration information for the service provider to use. The value of the property should contain a URL string (For example:iiops://localhost:7002
).java.naming.factory.initial:
property for specifying the initial context factory to use. The value of the property should be the fully qualified class name of the factory class that will create an initial context (For example:weblogic.jndi.WLInitialContextFactory
).
When setting the attribute, the syntax of its value is validated, and an
InvalidAttributeValueException
is thrown if the check fails. -
password(optional):
string(password)
The password for the user specified in the
Username
attribute for connecting to the datastore.When getting the value of this attribute, WebLogic Server does the following:
Retrieves the value of the
PasswordEncrypted
attribute.Decrypts the value and returns the unencrypted password as a String.
When you set the value of this attribute, WebLogic Server does the following:
Encrypts the value.
Sets the value of the
PasswordEncrypted
attribute to the encrypted value.
Note that use of the
Password
attribute is a potential security risk because the String object that contains the unencrypted password remains in the JVM's memory until garbage collection removes it and the memory is reallocated. Depending on how memory is allocated in the JVM, a significant amount of time could pass before this unencrypted data is removed from memory.Instead of using this attribute, use
PasswordEncrypted
-
realm(optional):
array Realm Reference
Title:
Realm Reference
Read Only:true
Contains the realm reference.Returns the realm that contains this RDBMS security store. Returns null if this RDBMS security store is not contained by a realm.
-
username(optional):
string
The username to use when connecting to the datastore.
Constraints
- legal null
array
Realm Reference
true
Returns the realm that contains this RDBMS security store. Returns null if this RDBMS security store is not contained by a realm.
-
Admin: basic
Type:
basic
Description:A user in the Admin security role.
Response
200 Response
Examples
Create this RDBMS security store optional singleton.
This example uses the POST method to create this RDBMS security store optional singleton.
Example Request
curl -v \ --user admin:admin123 \ -H X-Requested-By:MyClient \ -H Accept:application/json \ -H Content-Type:application/json \ -d "{ name: 'MyRDBMSSecurityStore', connectionURL: 'MyConnectionUrl', driverName: 'MyDriverName', username: 'MyUserName' }" \ -X POST http://localhost:7001/management/weblogic/latest/edit/securityConfiguration/realms/myrealm/RDBMSSecurityStore
Example Response
HTTP/1.1 201 Created Location: http://localhost:7001/management/weblogic/latest/edit/securityConfiguration/realms/myrealm/RDBMSSecurityStore Response Body: {}
Modify this RDBMS security store optional singleton.
This example uses the POST method to modify this RDBMS security store optional singleton.
Example Request
curl -v \ --user admin:admin123 \ -H X-Requested-By:MyClient \ -H Accept:application/json \ -H Content-Type:application/json \ -d "{ driverName: 'YourDriverName', username: 'YourUserName' }" \ -X POST http://localhost:7001/management/weblogic/latest/edit/securityConfiguration/realms/myrealm/RDBMSSecurityStore
Example Response
HTTP/1.1 200 OK Response Body: {}Back to Top