Chapter 1. Credentials and credential stores in Elytron 1.1. Types of credential stores provided by Elytron Elytron provides two default credential store types you can use to save your credentials: KeyStoreCredentialStore and PropertiesCredentialStore. You can manage credential stores with the JBoss EAP management CLI, or you can use the WildFly Elytron tool to manage them offline. In addition to the two default store types, you can also create, use, and manage your own custom credential stores. 1.1.1. KeyStoreCredentialStore/ credential-store in Elytron You can store all the Elytron credential types in a KeyStoreCredentialStore. The resource name for KeyStoreCredentialStore in the elytron subsystem is credential-store . The KeyStoreCredentialStore protects your credentials using the mechanisms provided by the KeyStore implementations in the Java Development Kit (JDK). Access a KeyStoreCredentialStore in the management CLI as follows: Additional resources Creating a credential-store for a standalone server Creating a credential-store for a managed domain Creating a credential-store using the WildFly Elytron tool Creating a credential-store using the Bouncy Castle provider credential-store attributes 1.1.2. PropertiesCredentialStore/ secret-key-credential-store in Elytron To start properly, JBoss EAP requires an initial key to unlock certain secure resources. Use the PropertiesCredentialStore to provide this initial secret key to unlock these necessary server resources. You can also use the PropertiesCredentialStore to store SecretKeyCredential, which supports storing Advanced Encryption Standard (AES) secret keys. Use file system permissions to restrict access to the credential store. Ideally, you should give access only to your application server to restrict access to this credential store. The resource name in the elytron subsystem for PropertiesCredentialStore is secret-key-credential-store , and you can access it in the management CLI as follows: Additional resources Creating a secret-key-credential-store for a standalone server Creating a secret-key-credential-store using WildFly Elytron tool secret-key-credential-store attributes 1.2. Credential types in Elytron Elytron provides the following three credential types to suit your various security needs, and you can store these credentials in one of Elytron's credential stores. PasswordCredential With this credential type, you can securely store plain text, or unencrypted, passwords. For the JBoss EAP resources that require a password, use a reference to the PasswordCredential instead of the plain text password to maintain the secrecy of the password. Example of connecting to a database In this example database connection command, you can see the password: StrongPassword . This means that others can also see it in the server configuration file. Example of connecting to a database using a PasswordCredential When you use a credential reference instead of a password to connect to a database, others can only see the credential reference in the configuration file, not your password KeyPairCredential You can use both Secure Shell (SSH) and Public-Key Cryptography Standards (PKCS) key pairs as KeyPairCredential. A key pair includes both a shared public key and a private key that only a given user knows. You can manage KeyPairCredential using only the WildFly Elytron tool. SecretKeyCredential A SecretKeyCredential is an Advanced Encryption Standard (AES) key that you can use to create encrypted expressions in Elytron. Additional resources Credential stores provided by Elytron Credential types supported by credential stores 1.3. Credential types supported by Elytron credential stores The following table illustrates which credential type is supported by which credential store: Credential type KeyStoreCredentialStore/credential-store PropertiesCredentialStore/secret-key-credential-store PasswordCredential Yes No KeyPairCredential Yes No SecretKeyCredential Yes Yes Additional resources Credential types in Elytron Credential stores provided by Elytron 1.4. Credential store operations using the JBoss EAP management CLI To manage JBoss EAP credentials in a running JBoss EAP server, use the provided management CLI operations. You can manage PasswordCredential and SecretKeyCredential using the JBoss EAP management CLI. Note You can do these operation only on modifiable credential stores. All credential store types are modifiable by default. 1.4.1. Creating a credential-store for a standalone server Create a credential-store for a JBoss EAP running as a standalone server in any directory on the file system. For security, the directory containing the store should be accessible to only limited users. Prerequisites You have provided at least read/write access to the directory containing the KeyStoreCredentialStore for the user account under which JBoss EAP is running. Note You cannot have the same name for a credential-store and a secret-key-credential-store because they implement the same Elytron capability: org.wildfly.security.credential-store . Procedure Create a KeyStoreCredentialStore using the following management CLI command: Syntax Example Additional resources KeyStoreCredentialStore/ credential-store in Elytron Credential store operations using the JBoss EAP management CLI credential-store attributes 1.4.2. Creating a credential-store for a managed domain You can create a credential-store in a managed domain, but you must first use the WildFly Elytron tool to prepare your KeyStoreCredentialStore. If you have multiple host controllers in a single managed domain, choose one of the following options: Create a credential-store in each host controller and add credentials to each credential-store . Copy a populated credential-store from one host controller to all the other host controllers. Save your credential-store file in your Network File System (NFS), then use that file for all the credential-store resources you create. Alternatively, you can create a credential-store file with credentials on a host controller without using the WildFly Elytron tool. Note You don't have to define a credential-store resource on every server, because every server on the same profile contains your credential-store file. You can find the credential-store file in the server data directory, relative-to=jboss.server.data.dir . Important You cannot have the same name for a credential-store and a secret-key-credential-store because they implement the same Elytron capability: org.wildfly.security.credential-store . The following procedure describes how to use the NFS to provide the credential-store file to all host controllers. Procedure Use the WildFly Elytron tool to create a credential-store storage file. For more information on this, see WildFly Elytron tool credential-store operations . Distribute the storage file. For example, allocate it to each host controller by using the scp command, or store it in your NFS and use it for all of your credential-store resources. Note To maintain consistency, for a credential-store file that multiple resources and host controllers use and which you stored in your NFS, you must use the credential-store in read-only mode. Additionally, make sure you provide an absolute path for your credential-store file. Syntax Example Optional: If you need to define the credential-store resource in a profile, use the storage file to create the resource. Syntax Example Optional: Create the credential-store resource for a host controller. Syntax Example Additional resources KeyStoreCredentialStore/ credential-store in Elytron Credential store operations using the WlidFly Elytron tool credential-store attributes 1.4.3. Creating a secret-key-credential-store for a standalone server Create a secret-key-credential-store using the management CLI. When you create a secret-key-credential-store , JBoss EAP generates a secret key by default. The name of the generated key is key and its size is 256-bit. Prerequisites JBoss EAP is running. You have provided at least read/write access to the directory containing the secret-key-credential-store for the user account under which JBoss EAP is running. Procedure Use the following command to create a secret-key-credential-store using the management CLI: Syntax Example 1.4.4. Adding a PasswordCredential to a credential-store Add a plain text password for those resources that require one as a PasswordCredential to the credential-store to hide that password in the configuration file. You can then reference this stored credential to access those resources, without ever exposing your password. Prerequisites You have created a credential-store . For information about creating a credential-store , see Creating a credential-store for a standalone server . Procedure Add a new PasswordCredential to a credential-store : Syntax Example Verification Issue the following command to verify that the PasswordCredential was added to the credential-store : Syntax Example Additional resources KeyStoreCredentialStore/ credential-store in Elytron credential-store attributes 1.4.5. Generating a SecretKeyCredential in a credential-store Generate a SecretKeyCredential in a credential-store . By default, Elytron creates a 256-bit key. If you want a different size, you can specify either a 128-bit or 192-bit key in the key-size attribute. Prerequisites You have created a credential-store . For information about creating a credential-store , see Creating a credential-store for a standalone server . Procedure Generate a SecretKeyCredential in a credential-store using the following management CLI command: Syntax Example Verification Issue the following command to verify that Elytron stored your SecretKeyCredential in the credential-store : Syntax Example Additional resources KeyStoreCredentialStore/ credential-store in Elytron credential-store attributes 1.4.6. Generating a SecretKeyCredential in a secret-key-credential-store Generate a SecretKeyCredential in a secret-key-credential-store . By default, Elytron creates a 256-bit key. If you want a different size, you can specify either a 128-bit or 192-bit key in the key-size attribute. When you generate a SecretKeyCredential, Elytron generates a new random secret key and stores it as the SecretKeyCredential. You can view the contents of the credential by using the export operation on the secret-key-credential-store . Important Make sure that you create a backup of either secret-key-credential-store , SecretKeyCredential, or both, because JBoss EAP cannot decrypt or retrieve lost Elytron credentials. You can use the export operation on the secret-key-credential-store to get the value of the SecretKeyCredential. You can then save this value as a backup. Prerequisites You have created a secret-key-credential-store . For information about creating a secret-key-credential-store , see Creating a secret-key-credential-store for a standalone server . Procedure Generate a SecretKeyCredential in a secret-key-credential-store using the following management CLI command: Syntax Example Verification Issue the following command to verify that Elytron created a SecretKeyCredential: Syntax Example Additional resources PropertiesCredentialStore/ secret-key-credential-store in Elytron secret-key-credential-store attributes 1.4.7. Importing a SecretKeyCredential to a secret-key-credential-store You can import a SecretKeyCredential created outside of the secret-key-credential-store into an Elytron secret-key-credential-store . Suppose you exported a SecretKeyCredential from another credential store - a credential-store , for example - you can import it to the secret-key-credential-store . Prerequisites You have created a secret-key-credential-store . For information about creating a secret-key-credential-store , see Creating a secret-key-credential-store for a standalone server . You have exported a SecretKeyCredential. For information about exporting a SecretKeyCredential, see Exporting a SecretKeyCredential from a secret-key-credential-store . Procedure Disable caching of commands in the management CLI using the following command: Important If you do not disable caching, the secret key is visible to anyone who can access the management CLI history file. Import the secret key using the following management CLI command: Syntax Example Re-enable the caching of commands using the following management CLI command: Additional resources PropertiesCredentialStore/ secret-key-credential-store in Elytron secret-key-credential-store attributes 1.4.8. Listing the credentials in a credential-store To view all the credentials stored in the credential-store , you can list them using the management CLI. Procedure List the credentials stored in a credential-store using the following management CLI command: Syntax Example Additional resources KeyStoreCredentialStore/ credential-store in Elytron credential-store attributes 1.4.9. Exporting a SecretKeyCredential from a credential-store You can export an existing SecretKeyCredential from a credential-store to use the SecretKeyCredential or to create a backup of the SecretKeyCredential. Prerequisites You have generated a SecretKeyCredential the credential-store . For information about generating a SecretKeyCredential in a credential-store , see Generating a SecretKeyCredential in a credential-store . Procedure Export a SecretKeyCredential from the credential-store using the following management CLI command: Syntax Example Additional resources KeyStoreCredentialStore/ credential-store in Elytron credential-store attributes 1.4.10. Exporting a SecretKeyCredential from a secret-key-credential-store You can export an existing SecretKeyCredential from a secret-key-credential-store to use the SecretKeyCredential or to create a backup of the SecretKeyCredential. Prerequisites You have either generated a SecretKeyCredential in the secret-key-credential-store or imported one to it. For information on generating a SecretKeyCredential in a secret-key-credential-store , Generating a SecretKeyCredential in a secret-key-credential-store . For information on importing a SecretKeyCredential to a secret-key-credential-store , see Importing a SecretKeyCredential to a secret-key-credential-store . Procedure Export a SecretKeyCredential from the secret-key-credential-store using the following management CLI command: Syntax Example Additional resources PropertiesCredentialStore/ secret-key-credential-store in Elytron secret-key-credential-store attributes 1.4.11. Removing a credential from credential-store You can store every credential type in the credential-store but, by default, when you remove a credential, Elytron assumes it's a PasswordCredential. If you want to remove a different credential type, specify it in the entry-type attribute. Procedure Remove a credential from the credential-store using the following management CLI command: Syntax Example removing a PasswordCredential Example removing a SecretKeyCredential Verification Issue the following command to verify that Elytron removed the credential: Syntax Example The credential you removed is not listed. Additional resources KeyStoreCredentialStore/ credential-store in Elytron credential-store attributes 1.4.12. Removing a credential from the secret-key-credential-store You can store only the SecretKeyCredential type in a secret-key-credential-store . This means that, when you remove a credential from a secret-key-credential-store , you don't have to specify an entry-type . Procedure Remove a SecretKeyCredential from the secret-key-credential-store using the following command: Syntax Example Verification Issue the following command to verify that Elytron removed the credential: Syntax Example The credential you removed is not listed. Additional resources PropertiesCredentialStore/ secret-key-credential-store in Elytron secret-key-credential-store attributes 1.5. Credential store operations using the WildFly Elytron tool You can perform various operations on credential stores offline using the WildFly Elytron tool. 1.5.1. Creating a credential-store using the WildFly Elytron tool In Elytron, you can create a credential-store offline where you can save all the credential types. Procedure Create a credential-store using the WildFly Elytron tool with the following command: Syntax Example If you don't want to include your store password in the command, omit that argument and then enter the password manually at the prompt. You can also use a masked password generated by the WildFly Elytron tool. For information about generating masked passwords, see Generating masked encrypted strings using the WildFly Elytron tool . Additional resources KeyStoreCredentialStore/ credential-store in Elytron Generating masked encrypted strings using the WildFly Elytron tool WildFly Elytron tool credential-store operations 1.5.2. Creating a credential-store using the Bouncy Castle provider Create a credential-store using the Bouncy Castle provider. Prerequisites Make sure that your environment is configured to use Bouncy Castle. Note You cannot have the same name for a credential-store and a secret-key-credential-store because they implement the same Elytron capability: org.wildfly.security.credential-store . Procedure Define a Bouncy Castle FIPS Keystore ( BCFKS ) keystore. FIPS stands for Federal Information Processing Standards. If you already have one, move on to the step. Important Make sure that the keystore keypass and storepass attributes are identical. If they aren't, the BCFKS keystore in the elytron subsystem can't define them. Generate a secret key for the credential-store . Define the credential-store using the WildFly Elytron tool with the following command: Additional resources KeyStoreCredentialStore/ credential-store in Elytron WildFly Elytron tool credential-store operations 1.5.3. Creating a secret-key-credential-store using WildFly Elytron tool In Elytron, you can create a secret-key-credential-store offline where you can save SecretKeyCredential instances. Procedure Create a PropertiesCredentialStore using the WildFly Elytron tool with the following command: Syntax Example Additional resources PropertiesCredentialStore/ secret-key-credential-store in Elytron WildFly Elytron tool secret-key-credential-store operations 1.5.4. WildFly Elytron tool credential-store operations You can do various credential-store tasks using the WildFly Elytron tool, including the following: Add a PasswordCredential You can add a PasswordCredential to a credential-store using the following WildFly Elytron tool command: Syntax Example If you don't want to put your secret in the command, omit that argument, then enter the secret manually when prompted. Generate a SecretKeyCredential You can add a SecretKeyCredential to a credential-store using the following WildFly Elytron tool command: Syntax Example If you don't want to put your secret in the command, omit that argument, then enter the secret manually when prompted. By default, when you create a SecretKeyCredential in JBoss EAP, you create a 256-bit secret key. If you want to change the size, you can specify --size=128 or --size=192 to create 128-bit or 192-bit keys respectively. Import a SecretKeyCredential You can import a SecretKeyCredential using the following WildFLy Elytron tool command: Syntax Example Enter the secret key you want to import. List all the credentials You can list the credentials in the credential-store using the following WildFly Elytron tool command: Syntax Example: Check if an alias exists Use the following command to check whether an alias exists in a credential store: Syntax Example Export a SecretKeyCredential You can export a SecretKeyCredential from a credential-store using the following command: Syntax Example Remove a credential You can remove a credential from a credential store using the following command: Syntax Example Additional resources KeyStoreCredentialStore/ credential-store in Elytron Credential types in Elytron 1.5.5. WildFly Elytron tool secret-key-credential-store operations You can do the following secret-key-credential-store operations for SecretKeyCredential using the WildFly Elytron tool: Generate a SecretKeyCredential You can generate a SecteKeyCredential in a secret-key-credential-store using the following WildFly Elytron tool command: Syntax Example Import a SecretKeyCredential You can import a SecretKeyCredential using the following WildFLy Elytron tool command: Syntax Example List all the credentials You can list the credentials in the secret-key-credential-store using the following WildFly Elytron tool command: Syntax Example Export a SecretKeyCredential You can export a SecretKeyCredential from a secret-key-credential-store using the following command: Syntax Example Remove a credential You can remove a credential from a credential store using the following command: Syntax Example Additional resources PropertiesCredentialStore/ secret-key-credential-store in Elytron Credential types in Elytron 1.5.6. Adding a credential-store created with the WildFly Elytron tool to a JBoss EAP Server After you have created a credential-store with the WildFly Elytron tool, you can add it to your running JBoss EAP server. Prerequisites You have created a credential store with the WildFly Elytron tool. For more information, see Creating a credential-store using the WildFly Elytron tool . Procedure Add the credential store to your running JBoss EAP server with the following management CLI command: Syntax Example After adding the credential store to the JBoss EAP configuration, you can then refer to a password or sensitive string stored in the credential store using the credential-reference attribute. For more information, use the EAP_HOME /bin/elytron-tool.sh credential-store --help command for a detailed listing of available options. Additional resources credential-store attributes 1.5.7. WildFly Elytron tool key pair management operations You can use the following arguments to operate the elytron-tool.sh to manipulate a credential store, such as generating a new key pair that you can store under an alias in a credential store. Generate a key pair Use the generate-key-pair command to create a key pair. You can then store the key pair under an alias in the credential store. The following example shows the creation of an RSA key pair, which has an allocated size of 3072 bits that is stored in the location specified for the credential store. The alias given to the key pair is example . Import a key pair Use the import-key-pair command to import an existing SSH key pair into a credential store with a specified alias. The following example imports a key pair with the alias of example from the /home/user/.ssh/id_rsa file containing the private key in the OpenSSH format: Export a key pair Use the export-key-pair-public-key command to display the public key of a key pair. The public key has a specified alias in the OpenSSH format. The following example displays the public key for the alias example : Note After issuing the export-key-pair-public-key command, you are prompted to enter the credential store passphrase. If no passphrase exists, leave the prompt blank. 1.5.8. Example use of stored key pair in the Elytron configuration files A key pair consists of two separate, but matching, cryptographic keys: a public key and a private key. You need to store a key pair in a credential store before you can reference the key pair in an elytron configuration file. You can then provide Git with access to manage your standalone server configuration data. The following example references a credential store and its properties in the <credential-stores> element of an elytron configuration file. The <credential> element references the credential store and the alias, which stores the key pair. <?xml version="1.0" encoding="UTF-8"?> <configuration> <authentication-client xmlns="urn:elytron:client:1.6"> <credential-stores> <credential-store name=" USD{credential_store_name} "> <protection-parameter-credentials> <clear-password password=" USD{credential_store_password} "/> </protection-parameter-credentials> <attributes> <attribute name="path" value=" USD{path_to_credential_store} "/> </attributes> </credential-store> </credential-stores> <authentication-rules> <rule use-configuration=" USD{configuration_file_name} "/> </authentication-rules> <authentication-configurations> <configuration name=" USD{configuration_file_name} "> <credentials> <credential-store-reference store=" USD{credential_store_name} " alias=" USD{alias_of_key_pair} "/> </credentials> </configuration> </authentication-configurations> </authentication-client> </configuration> After you configure the elytron configuration file, the key pair can be used for SSH authentication. Additional resources WildFly Elytron tool key pair management operations 1.5.9. Generating masked encrypted strings using the WildFly Elytron tool You can use the WildFly Elytron tool to generate encrypted strings to use instead of a plain text password for a credential store. Procedure To generate a masked string, use the following command and provide values for the salt and the iteration count: For example: If you do not want to provide the secret in the command, you can omit that argument and you will be prompted to enter the secret manually using standard input. For more information, use the EAP_HOME /bin/elytron-tool.sh mask --help command for a detailed listing of available options. 1.6. Automatic update of credentials in credential store If you have a credential store, you are not required to add credentials or update existing credentials before you can reference them from a credential reference. Elytron automates this process. When configuring a credential reference, specify both the store and clear-text attributes. Elytron automatically adds or updates a credential in the credential store specified by the store attribute. Optionally, you can specify the alias attribute. Elytron updates the credential store as follows: If you specify an alias: If an entry for the alias exists, the existing credential is replaced with the specified clear text password. If an entry for the alias does not exist, a new entry is added to the credential store with the specified alias and the clear text password. If you do not specify an alias, Elytron generates an alias and adds a new entry to the credential store with the generated alias and the specified clear text password. The clear-text attribute is removed from the management model when the credential store is updated. The following example illustrates how to create a credential reference that specifies the store , clear-text , and alias attributes: You can update the credential for the myNewAlias entry that was added to the previously defined credential store with the following command: Note If an operation that includes a credential-reference parameter fails, no automatic credential store update occurs. The credential store that was specified by the credential-reference attribute does not change. 1.7. Example of using a credential store with Elytron client Clients connecting to JBoss EAP, such as Jakarta Enterprise Beans, can authenticate using Elytron Client. Users without access to a running JBoss EAP server can create and modify credential stores using the WildFly Elytron tool, and then clients can use Elytron Client to access sensitive strings inside a credential store. The following example shows you how to use a credential store in an Elytron Client configuration file. Example custom-config.xml with a Credential Store <configuration> <authentication-client xmlns="urn:elytron:client:1.7"> ... <credential-stores> <credential-store name="my_store"> 1 <protection-parameter-credentials> <credential-store-reference clear-text="pass123"/> 2 </protection-parameter-credentials> <attributes> <attribute name="location" value="/path/to/my_store.jceks"/> 3 </attributes> </credential-store> </credential-stores> ... <authentication-configurations> <configuration name="my_user"> <set-host name="localhost"/> <set-user-name name="my_user"/> <set-mechanism-realm name="ManagementRealm"/> <use-provider-sasl-factory/> <credentials> <credential-store-reference store="my_store" alias="my_user"/> 4 </credentials> </configuration> </authentication-configurations> ... </authentication-client> </configuration> 1 A name for the credential store for use within the Elytron Client configuration file. 2 The password for the credential store. 3 The path to the credential store file. 4 The credential reference for a sensitive string stored in the credential store. Additional resources Credential store operations using the WildFly Elytron tool . 1.8. Creating FIPS 140-2 compliant credential stores You can configure Federal Information Processing Standard (FIPS) 140-2 compliant credential store in Elytron. FIPS 140-2, is a computer security standard, developed by a U.S. Government industry working group to validate the quality of cryptographic modules. FIPS publications (including 140-2) can be found at the URL: http://csrc.nist.gov/publications/PubsFIPS.html . You can configure FIPS 140-2 compliant credential store in Elytron using two different providers: SunPKCS#11 provider and Network Security Services (NSS) database. For more information, see Creating FIPS 140-2 compliant credential store using a SunPKCS#11 provider and NSS database . BouncyCastle providers. For more information, see Creating FIPS 140-2 compliant credential store using BouncyCastle providers . Important JBoss EAP itself is not FIPS-certified. The level of FIPS support in JBoss EAP is that JBoss EAP can be used with FIPS-certified cryptographic implementations. The implementations tested are BouncyCastle and SunPKCS#11. 1.8.1. Creating FIPS 140-2 compliant credential store using a SunPKCS#11 provider and NSS database NSS is a set of libraries that support cross-platform security-enabled client and server applications. You can use SunPKCS#11 provider with NSS library in JBoss EAP to implement FIPS 140-2 compliant cryptography. For information about NSS, see Mozilla docs - Network Security Services (NSS) . For information about SunPKCS#11 provider, see PKCS#11 Reference Guide . 1.8.1.1. JDKs that support FIPS when using a SunPKCS#11 provider and NSS database Not all Java Development Kit (JDK) vendors support configuring the SunPKCS#11 security provider with a Network Security Services (NSS) software token, implemented by the NSS library, required for Federal Information Processing Standard (FIPS) 140-2 compliance. Ensure that your JDK supports it before configuring FIPS with the SunPKCS#11 provider and NSS database in JBoss EAP. The following is a list of supported JDKs for JBoss EAP that support configuring SunPKCS#11 security: OpenJDK 11 OpenJDK 17 Additional resources Configuring OpenJDK 11 on RHEL with FIPS Configuring OpenJDK 17 on RHEL with FIPS 1.8.1.2. Creating FIPS 140-2 compliant credential store using a SUNPKCS#11 provider and NSS database in FIPS enabled RHEL Starting with Red Hat Enterprise Linux 8.4, if you enable the Federal Information Processing Standard (FIPS) system-wide crypto policy, FIPS for Java is also enabled automatically. You can use the default Network Security Services (NSS) database to create a FIPS 140-2 compliant credential store. In this procedure USDJAVA_HOME refers to the JDK installation path. Run the commands in this procedure as the root user. Prerequisites FIPS is enabled in RHEL. You can check whether FIPS is enabled using the following command: For information about enabling FIPS in RHEL, see the following resources: Installing the system in FIPS mode in the Red Hat Enterprise Linux documentation. Switching the system to FIPS mode in the Red Hat Enterprise Linux documentation. NSS tools are installed. In Red Hat Enterprise Linux you can install NSS tools using the DNF package manager as follows: Your Java Development Kit (JDK) supports configuration of PKCS#11 with an NSS library. For information about JDKs that support FIPS, see JDKs that support FIPS . JBoss EAP is running. Procedure Update the value of nssDbMode in the USDJAVA_HOME/conf/security/nss.fips.cfg file to readWrite . Example nss.fips.cfg contents Generate an AES secret key to encrypt the credential stores. Note You must use store password NONE in the command. Syntax Example Verify that you can read the secret key. Update the value of nssDbMode in the USDJAVA_HOME/conf/security/nss.fips.cfg file to readOnly . Example nss.fips.cfg contents Add the SunJCE provider to the list of providers in the management CLI. Add a provider loader for SunJCE. Configure Elytron and SunJCE in an aggregate provider. Syntax Example Note The providers are called in the order that they are defined in the command. Use the SunJCE provider to create a credential store in Elytron. Syntax Example Verification Add an alias to the credential store. Syntax Example List the aliases in the credential store. Syntax Example The created credential store is FIPS 140-2 compliant. Additional resources aggregate-providers attributes credential-store attributes credential-store implementation properties 1.8.2. Creating FIPS 140-2 compliant credential store using BouncyCastle providers BouncyCastle provides lightweight cryptography APIs for Java and C#. You can use the following BouncyCastle providers with JBoss EAP for creating FIPS 140-2 compliant credential stores: BouncyCastle FIPS provider for the Java Cryptography Extension (JCE) and the Java Cryptography Architecture (JCA). BouncyCastle FIPS provider for the Java Secure Socket Extension (JSSE). For information about BouncyCastle, see The Legion of the Bouncy Castle . 1.8.2.1. Creating FIPS 140-2 compliant credential store using BouncyCastle providers Starting with Red Hat Enterprise Linux 8.4, if you enable the Federal Information Processing Standard (FIPS) system-wide crypto policy, OpenJDK automatically enables different security providers. One of the security providers is the SunPKCS11 provider configured in FIPS mode. You can instead use the BouncyCastle providers to create a Federal Information Processing Standard (FIPS) 140-2 compliant credential store by following the below steps. Prerequisites FIPS is enabled in RHEL. You can check whether FIPS is enabled using the following command: For information about enabling FIPS in RHEL, see the following resources: Installing the system in FIPS mode in the Red Hat Enterprise Linux documentation. Switching the system to FIPS mode in the Red Hat Enterprise Linux documentation. Your Java Development Kit (JDK) supports the configuration of FIPS using BouncyCastle providers. For more information, see Java Related Questions on the Legion of the Bouncy Castle - FIPS Resources Page. Procedure Download the BouncyCastle jars from the following links: bc-fips- N jar: Bouncy Castle Provider (FIPS Distribution) Maven . bctls-fips- N jar: Bouncy Castle TLS/JSSE APIs (FIPS Distribution) . Where N stands for the BouncyCastle FIPS provider version. You can find information about the latest certified version of BouncyCastle FIPS provider that conforms to your environment at The Legion of the Bouncy Castle . Create a configuration file called java.security with the following contents: Note Do not modify the FIPS providers in the default java.security file. It is recommended to use your own java.security properties file as described in this procedure. Generate an AES secret key to encrypt the credential stores. Syntax Example Verify that you can read the secret key. Syntax Example Example output Start the server. Configure JBoss EAP to use BouncyCastle providers using the management CLI. Add SunJCE provider to the list of providers. Add BouncyCastle provider jar as a module in JBoss EAP. Syntax Example Add the provider loader for the BouncyCastle providers. Syntax Example Configure BouncyCastle, SunJCE and combined-providers in an aggregate provider. Syntax Example Note The providers are called in the order that they are defined in the command. Reload the server. Use the BouncyCastle providers to create a credential store in Elytron. Syntax Example Verification Add an alias to the credential store. Syntax Example List the aliases in the credential store. Syntax Example The created credential store is FIPS 140-2 compliant. Additional resources aggregate-providers attributes credential-store attributes credential-store implementation properties provider-loader attributes To learn more about the module add command, you can run the --help command in the JBoss EAP management CLI:

Commands:
/subsystem=elytron/credential-store
/subsystem=elytron/secret-key-credential-store
data-source add ... --user-name=db_user --password=StrongPassword
data-source add ... --user-name=db_user --credential-reference={store=exampleKeyStoreCredentialStore, alias=passwordCredentialAlias}
/subsystem=elytron/credential-store= <name_of_credential_store> :add(path=" <path_to_store_file> ", relative-to= <base_path_to_store_file> , credential-reference={clear-text= <store_password> }, create=true)
/subsystem=elytron/credential-store=exampleKeyStoreCredentialStore:add(path="exampleKeyStoreCredentialStore.jceks", relative-to=jboss.server.data.dir, credential-reference={clear-text=password}, create=true) {"outcome" => "success"}
/profile= <profile_name> /subsystem=elytron/credential-store= <name_of_credential_store> :add(path= <absolute_path_to_store_keystore> ,credential-reference={clear-text=" <store_password> "},create=false,modifiable=false)
/profile=full-ha/subsystem=elytron/credential-store=exampleCredentialStoreDomain:add(path=/usr/local/etc/example-cred-store.cs,credential-reference={clear-text="password"},create=false,modifiable=false)
/profile= <profile_name> /subsystem=elytron/credential-store= <name_of_credential_store> :add(path= <path_to_store_file> ,credential-reference={clear-text=" <store_password> "})
/profile=full-ha/subsystem=elytron/credential-store=exampleCredentialStoreHA:add(path=/usr/local/etc/example-cred-store-ha.cs, credential-reference={clear-text="password"})
/host= <host_controller_name> /subsystem=elytron/credential-store= <name_of_credential_store> :add(path= <path_to_store_file> ,credential-reference={clear-text=" <store_password> "})
/host=master/subsystem=elytron/credential-store=exampleCredentialStoreHost:add(path=/usr/local/etc/example-cred-store-host.cs, credential-reference={clear-text="password"})
/subsystem=elytron/secret-key-credential-store= <name_of_credential_store> :add(path=" <path_to_the_credential_store> ", relative-to= <path_to_store_file> )
/subsystem=elytron/secret-key-credential-store=examplePropertiesCredentialStore:add(path=examplePropertiesCredentialStore.cs, relative-to=jboss.server.config.dir) {"outcome" => "success"}
/subsystem=elytron/credential-store= <name_of_credential_store> :add-alias(alias= <alias> , secret-value= <secret-value> )
/subsystem=elytron/credential-store=exampleKeyStoreCredentialStore:add-alias(alias=passwordCredentialAlias, secret-value=StrongPassword) {"outcome" => "success"}
/subsystem=elytron/credential-store= <name_of_credential_store> :read-aliases()
/subsystem=elytron/credential-store=exampleKeyStoreCredentialStore:read-aliases() { "outcome" => "success", "result" => ["passwordcredentialalias"] }
/subsystem=elytron/credential-store= <name_of_credential_store> :generate-secret-key(alias= <alias> , key-size= <128_or_192> )
/subsystem=elytron/credential-store=exampleKeyStoreCredentialStore:generate-secret-key(alias=secretKeyCredentialAlias)
/subsystem=elytron/credential-store= <name_of_credential_store> :read-aliases()
/subsystem=elytron/credential-store=exampleKeyStoreCredentialStore:read-aliases() { "outcome" => "success", "result" => [ "secretkeycredentialalias" ] }
/subsystem=elytron/secret-key-credential-store= <name_of_the_properties_credential_store> :generate-secret-key(alias= <alias> , key-size= <128_or_192> )
/subsystem=elytron/secret-key-credential-store=examplePropertiesCredentialStore:generate-secret-key(alias=secretKeyCredentialAlias) {"outcome" => "success"}
/subsystem=elytron/secret-key-credential-store= <name_of_the_properties_credential_store> :read-aliases()
/subsystem=elytron/secret-key-credential-store=examplePropertiesCredentialStore:read-aliases() { "outcome" => "success", "result" => [ "secretkeycredentialalias", "key" ] }
history --disable
/subsystem=elytron/secret-key-credential-store= <name_of_credential_store> :import-secret-key(alias= <alias> , key=" <secret_key> ")
/subsystem=elytron/secret-key-credential-store=examplePropertiesCredentialStore:import-secret-key(alias=imported, key="RUxZAUs+Y1CzEPw0g2AHHOZ+oTKhT9osSabWQtoxR+O+42o11g==")
history --enable
/subsystem=elytron/credential-store= <name_of_credential_store> :read-aliases()
{ "outcome" => "success", "result" => [ "passwordcredentialalias", "secretkeycredentialalias" ] }
/subsystem=elytron/credential-store= <name_of_credential_store> :export-secret-key(alias= <alias> )
/subsystem=elytron/credential-store=exampleKeyStoreCredentialStore:export-secret-key(alias=secretKeyCredentialAlias) { "outcome" => "success", "result" => {"key" => "RUxZAUui+8JkoDCE6mFyA3cCIbSAZaXq5wgYejj1scYgdDqWiw=="} }
/subsystem=elytron/secret-key-credential-store= <name_of_credential_store> :export-secret-key(alias= <alias> )
/subsystem=elytron/secret-key-credential-store=examplePropertiesCredentialStore:export-secret-key(alias=secretkeycredentialalias) { "outcome" => "success", "result" => {"key" => "RUxZAUtxXcYvz0aukZu+odOynIr0ByLhC72iwzlJsi+ZPmONgA=="} }
/subsystem=elytron/credential-store= <name_of_credential_store> :remove-alias(alias= <alias> , entry-type= <credential_type> )
/subsystem=elytron/credential-store=exampleKeyStoreCredentialStore:remove-alias(alias=passwordCredentialAlias) { "outcome" => "success", "response-headers" => {"warnings" => [{ "warning" => "Update dependent resources as alias 'passwordCredentialAlias' does not exist anymore", "level" => "WARNING", "operation" => { "address" => [ ("subsystem" => "elytron"), ("credential-store" => "exampleKeyStoreCredentialStore") ], "operation" => "remove-alias" } }]} }
/subsystem=elytron/credential-store=exampleKeyStoreCredentialStore:remove-alias(alias=secretKeyCredentialAlias, entry-type=SecretKeyCredential) { "outcome" => "success", "response-headers" => {"warnings" => [{ "warning" => "Update dependent resources as alias 'secretKeyCredentialAl ias' does not exist anymore", "level" => "WARNING", "operation" => { "address" => [ ("subsystem" => "elytron"), ("credential-store" => "exampleKeyStoreCredentialStore") ], "operation" => "remove-alias" } }]} }
/subsystem=elytron/credential-store= <name_of_credential_store> :read-aliases()
/subsystem=elytron/credential-store=exampleKeyStoreCredentialStore:read-aliases() { "outcome" => "success", "result" => [] }
/subsystem=elytron/secret-key-credential-store= <name_of_credential_store> :remove-alias(alias= <alias> )
/subsystem=elytron/secret-key-credential-store=examplePropertiesCredentialStore:remove-alias(alias=secretKeyCredentialAlias) { "outcome" => "success", "response-headers" => {"warnings" => [{ "warning" => "Update dependent resources as alias 'secretKeyCredentialAlias' does not exist anymore", "level" => "WARNING", "operation" => { "address" => [ ("subsystem" => "elytron"), ("secret-key-credential-store" => "examplePropertiesCredentialSt ore") ], "operation" => "remove-alias" } }]} }
/subsystem=elytron/secret-key-credential-store= <name_of_credential_store> :read-aliases()
/subsystem=elytron/secret-key-credential-store=examplePropertiesCredentialStore:read-aliases() { "outcome" => "success", "result" => [] }
EAP_HOME /bin/elytron-tool.sh credential-store --create --location " <path_to_store_file> " --password <store_password>
EAP_HOME /bin/elytron-tool.sh credential-store --create --location "../cred_stores/example-credential-store.jceks" --password storePassword Credential Store has been successfully created
keytool -genkeypair -alias <key_pair_alias> -keyalg <key_algorithm> -keysize <key_size> -storepass <key_pair_and_keystore_password> -keystore <path_to_keystore> -storetype BCFKS -keypass <key_pair_and_keystore_password>
keytool -genseckey -alias <key_alias> -keyalg <key_algorithm> -keysize <key_size> -keystore <path_to_keystore> -storetype BCFKS -storepass <key_and_keystore_password> -keypass <key_and_keystore_password>
EAP_HOME/bin/elytron-tool.sh credential-store -c -a <alias> -x <alias_password> -p <key_and_keystore_password> -l <path_to_keystore> -u "keyStoreType=BCFKS;external=true;keyAlias= <key_alias> ;externalPath= <path_to_credential_store> "
EAP_HOME /bin/elytron-tool.sh credential-store --create --location " <path_to_store_file> " --type PropertiesCredentialStore
bin/elytron-tool.sh credential-store --create --location=standalone/configuration/properties-credential-store.cs --type PropertiesCredentialStore Credential Store has been successfully created
EAP_HOME /bin/elytron-tool.sh credential-store --location " <path_to_store_file> " --password <store_password> --add <alias> --secret <sensitive_string>
EAP_HOME /bin/elytron-tool.sh credential-store --location "../cred_stores/example-credential-store.jceks" --password storePassword --add examplePasswordCredential --secret speci@l_db_paUSDUSD_01 Alias "examplePasswordCredential" has been successfully stored
EAP_HOME /bin/elytron-tool.sh credential-store --generate-secret-key=example --location= <path_to_the_credential_store> --password <store_password>
EAP_HOME /bin/elytron-tool.sh credential-store --generate-secret-key=example --location "../cred_stores/example-credential-store.jceks" --password storePassword Alias "example" has been successfully stored
EAP_HOME /bin/elytron-tool.sh credential-store --import-secret-key=imported --location= <path_to_credential_store> --password= <store_password>
EAP_HOME /bin/elytron-tool.sh credential-store --import-secret-key=imported --location=../cred_stores/example-credential-store.jceks --password=storePassword
EAP_HOME /bin/elytron-tool.sh credential-store --location " <path_to_store_file> " --password <store_password> --aliases
EAP_HOME /bin/elytron-tool.sh credential-store --location "../cred_stores/example-credential-store.jceks" --password storePassword --aliases Credential store contains following aliases: examplepasswordcredential example
EAP_HOME /bin/elytron-tool.sh credential-store --location " <path_to_store_file> " --password <store_password> --exists <alias>
EAP_HOME /bin/elytron-tool.sh credential-store --location "../cred_stores/example-credential-store.jceks" --password storePassword --exists examplepasswordcredential Alias "examplepasswordcredential" exists
EAP_HOME /bin/elytron-tool.sh credential-store --export-secret-key= <alias> --location= <path_to_credential_store> --password=storePassword
EAP_HOME /bin/elytron-tool.sh credential-store --export-secret-key=example --location=../cred_stores/example-credential-store.jceks --password=storePassword Exported SecretKey for alias example=RUxZAUtBiAnoLP1CA+i6DtcbkZHfybBJxPeS9mlVOmEYwjjmEA==
EAP_HOME /bin/elytron-tool.sh credential-store --location " <path_to_store_file> " --password <store_password> --remove <alias>
EAP_HOME /bin/elytron-tool.sh credential-store --location "../cred_stores/example-credential-store.jceks" --password storePassword --remove examplepasswordcredential Alias "examplepasswordcredential" has been successfully removed
EAP_HOME /bin/elytron-tool.sh credential-store --generate-secret-key=example --location " <path_to_the_credential_store> " --type PropertiesCredentialStore
EAP_HOME /bin/elytron-tool.sh credential-store --generate-secret-key=example --location "standalone/configuration/properties-credential-store.cs" --type PropertiesCredentialStore Alias "example" has been successfully stored
EAP_HOME /bin/elytron-tool.sh credential-store --import-secret-key=imported --location= <path_to_credential_store> --type PropertiesCredentialStore
EAP_HOME /bin/elytron-tool.sh credential-store --import-secret-key=imported --location "standalone/configuration/properties-credential-store.cs" --type PropertiesCredentialStore
EAP_HOME /bin/elytron-tool.sh credential-store --location " <path_to_store_file> " --aliases --type PropertiesCredentialStore
EAP_HOME /bin/elytron-tool.sh credential-store --location "standalone/configuration/properties-credential-store.cs" --aliases --type PropertiesCredentialStore Credential store contains following aliases: example
EAP_HOME /bin/elytron-tool.sh credential-store --export-secret-key= <alias> --location " <path_to_credential_store> " --type PropertiesCredentialStore
EAP_HOME /bin/elytron-tool.sh credential-store --export-secret-key=example --location "standalone/configuration/properties-credential-store.cs" --type PropertiesCredentialStore Exported SecretKey for alias example=RUxZAUt1EZM7PsYRgMGypkGirSel+5Eix4aSgwop6jfxGYUQaQ==
EAP_HOME /bin/elytron-tool.sh credential-store --location " <path_to_store_file> " --remove <alias> --type PropertiesCredentialStore
EAP_HOME /bin/elytron-tool.sh credential-store --location "standalone/configuration/properties-credential-store.cs" --remove example --type PropertiesCredentialStore Alias "example" has been successfully removed
/subsystem=elytron/credential-store= <store_name> :add(location=" <path_to_store_file> ",credential-reference={clear-text= <store_password> })
/subsystem=elytron/credential-store=my_store:add(location="../cred_stores/example-credential-store.jceks",credential-reference={clear-text=storePassword})
EAP_HOME /bin/elytron-tool.sh credential-store --location= <path_to_store_file> --generate-key-pair example --algorithm RSA --size 3072
EAP_HOME /bin/elytron-tool.sh credential-store --import-key-pair example --private-key-location /home/user/.ssh/id_rsa --location= <path_to_store_file>
EAP_HOME /bin/elytron-tool.sh credential-store --location= <path_to_store_file> --export-key-pair-public-key example Credential store password: Confirm credential store password: ecdsa-sha2-nistp256 AAAAE2VjZHNhLXNoYTItbmlzdHAyNTYAAAAIbmlzdHAyNTYAAABBBMfncZuHmR7uglb0M96ieArRFtp42xPn9+ugukbY8dyjOXoi cZrYRyy9+X68fylEWBMzyg+nhjWkxJlJ2M2LAGY=
<?xml version="1.0" encoding="UTF-8"?> <configuration> <authentication-client xmlns="urn:elytron:client:1.6"> <credential-stores> <credential-store name=" USD{credential_store_name} "> <protection-parameter-credentials> <clear-password password=" USD{credential_store_password} "/> </protection-parameter-credentials> <attributes> <attribute name="path" value=" USD{path_to_credential_store} "/> </attributes> </credential-store> </credential-stores> <authentication-rules> <rule use-configuration=" USD{configuration_file_name} "/> </authentication-rules> <authentication-configurations> <configuration name=" USD{configuration_file_name} "> <credentials> <credential-store-reference store=" USD{credential_store_name} " alias=" USD{alias_of_key_pair} "/> </credentials> </configuration> </authentication-configurations> </authentication-client> </configuration>
EAP_HOME /bin/elytron-tool.sh mask --salt <salt> --iteration <iteration_count> --secret <password>
EAP_HOME /bin/elytron-tool.sh mask --salt 12345678 --iteration 123 --secret supersecretstorepassword MASK-8VzWsSNwBaR676g8ujiIDdFKwSjOBHCHgnKf17nun3v;12345678;123
/subsystem=elytron/key-store=exampleKS:add(relative-to=jboss.server.config.dir, path=example.keystore, type=JCEKS, credential-reference={store=exampleKeyStoreCredentialStore, alias=myNewAlias, clear-text=myNewPassword}) { "outcome" => "success", "result" => {"credential-store-update" => { "status" => "new-entry-added", "new-alias" => "myNewAlias" }} }
/subsystem=elytron/key-store=exampleKS:write-attribute(name=credential-reference.clear-text,value=myUpdatedPassword) { "outcome" => "success", "result" => {"credential-store-update" => {"status" => "existing-entry-updated"}}, "response-headers" => { "operation-requires-reload" => true, "process-state" => "reload-required" } }
<configuration> <authentication-client xmlns="urn:elytron:client:1.7"> <credential-stores> <credential-store name="my_store"> 1 <protection-parameter-credentials> <credential-store-reference clear-text="pass123"/> 2 </protection-parameter-credentials> <attributes> <attribute name="location" value="/path/to/my_store.jceks"/> 3 </attributes> </credential-store> </credential-stores> <authentication-configurations> <configuration name="my_user"> <set-host name="localhost"/> <set-user-name name="my_user"/> <set-mechanism-realm name="ManagementRealm"/> <use-provider-sasl-factory/> <credentials> <credential-store-reference store="my_store" alias="my_user"/> 4 </credentials> </configuration> </authentication-configurations> </authentication-client> </configuration>
fips-mode-setup --check
dnf install -y nss-tools
name = NSS-FIPS nssLibraryDirectory = /usr/lib64 nssSecmodDirectory = sql:/etc/pki/nssdb nssDbMode = readWrite nssModule = fips attributes(*,CKO_SECRET_KEY,CKK_GENERIC_SECRET)={ CKA_SIGN=true }
keytool -genseckey -keystore NONE -storetype PKCS11 -storepass NONE -alias <key_alias> -keyalg <symmetric_key_algorithm> -keysize <key_size>
keytool -genseckey -keystore NONE -storetype PKCS11 -storepass NONE -alias exampleKeyAlias -keyalg AES -keysize 256
keytool -list -storetype pkcs11 -storepass NONE Keystore type: PKCS11 Keystore provider: SunPKCS11-NSS-FIPS Your keystore contains 1 entry exampleKeyAlias, SecretKeyEntry,
name = NSS-FIPS nssLibraryDirectory = /usr/lib64 nssSecmodDirectory = sql:/etc/pki/nssdb nssDbMode = readOnly nssModule = fips attributes(*,CKO_SECRET_KEY,CKK_GENERIC_SECRET)={ CKA_SIGN=true }
/subsystem=elytron/provider-loader=SunJCE:add(class-names=[com.sun.crypto.provider.SunJCE]) {"outcome" => "success"}
/subsystem=elytron/aggregate-providers= <aggregate_provider_name> :add(providers=[elytron,SunJCE])
/subsystem=elytron/aggregate-providers=exampleAggregateProvider:add(providers=[elytron,SunJCE]) {"outcome" => "success"}
/subsystem=elytron/credential-store= <credential_store_name> :add(implementation-properties={keyStoreType => PKCS11, external => true, keyAlias => <key_alias> , externalPath => <path_where_credential_store_is_to_be_saved> }, modifiable=true, credential-reference={clear-text= <password> }, create=true, other-providers= <aggregate_provider_name> )
/subsystem=elytron/credential-store=exampleFipsCredentialStore:add(implementation-properties={keyStoreType => PKCS11, external => true, keyAlias => exampleKeyAlias, externalPath => /home/ashwin/example.store}, modifiable=true, credential-reference={clear-text=secret}, create=true, other-providers=exampleAggregateProvider) {"outcome" => "success"}
/subsystem=elytron/credential-store= <credential_store_name> :add-alias(alias= <alias> , secret-value= <secret_value> )
/subsystem=elytron/credential-store=exampleFipsCredentialStore:add-alias(alias=exampleAlias, secret-value=secret) {"outcome" => "success"}
/subsystem=elytron/credential-store= <credential_store_name> :read-aliases()
/subsystem=elytron/credential-store=exampleFipsCredentialStore:read-aliases() { "outcome" => "success", "result" => ["examplealias"] }
fips-mode-setup --check
fips.provider.1=org.bouncycastle.jcajce.provider.BouncyCastleFipsProvider fips.provider.2=org.bouncycastle.jsse.provider.BouncyCastleJsseProvider fips:BCFIPS fips.provider.3=SUN fips.provider.4=SunEC fips.provider.5=com.sun.net.ssl.internal.ssl.Provider
keytool -J-Djava.security.properties= <java_security_file> -genseckey -keystore " <keystore_name> " -storetype BCFKS -storepass <store_password> -alias <key_alias> -keyalg <symmetric_key_algorithm> -keysize <key_size> -keypass <key_password> -provider org.bouncycastle.jcajce.provider.BouncyCastleFipsProvider -providerpath <path_to_bc-fips_jar> -dname " <certificate_contents> " -validity <validity_in_days>
keytool -J-Djava.security.properties= <path_to_java_security_file> /java.security -genseckey -keystore "examplekeystore.bcfks" -storetype BCFKS -storepass password -alias exampleKeyAlias -keyalg AES -keysize 256 -keypass password -provider org.bouncycastle.jcajce.provider.BouncyCastleFipsProvider -providerpath <path_to_bc-fips_jar> /bc-fips-1.0.2.jar -dname "CN=localhost" -validity 365
keytool -J-Djava.security.properties= <java_security_file> -list -keystore <keystore_name> -storetype BCFKS -storepass <store_password> -provider org.bouncycastle.jcajce.provider.BouncyCastleFipsProvider -providerpath <path_to_bc-fips_jar>
keytool -J-Djava.security.properties= <path_to_java_security_file> /java.security -list -keystore examplekeystore.bcfks -storetype BCFKS -storepass password -provider org.bouncycastle.jcajce.provider.BouncyCastleFipsProvider -providerpath <path_to_bc-fips_jar> /bc-fips-1.0.2.jar
Keystore type: BCFKS Keystore provider: BCFIPS Your keystore contains 1 entry exampleKeyAlias, Mar 1, 2023, SecretKeyEntry,
/subsystem=elytron/provider-loader=SunJCE:add(class-names=[com.sun.crypto.provider.SunJCE])
module add --name=org.bouncycastle.fips --resources= <path_to_bc-fips_jar> : <path_to_bctls-fips_jar>
module add --name=org.bouncycastle.fips --resources= <path_to_bc-fips_jar> /bc-fips-1.0.2.jar: <path_to_bctls-fips_jar> /bctls-fips-1.0.2.jar
/subsystem=elytron/provider-loader= <provider_loader_name> :add(module=org.bouncycastle.fips)
/subsystem=elytron/provider-loader=exampleProviderLoader:add(module=org.bouncycastle.fips)
/subsystem=elytron/aggregate-providers= <aggregate_provider_name> :add(providers=[ <provider_loader_name> ,SunJCE,combined-providers])
/subsystem=elytron/aggregate-providers=exampleAggregateProvider:add(providers=[exampleProviderLoader,SunJCE,combined-providers])
reload
/subsystem=elytron/credential-store= <credential_store_name> :add(credential-reference={clear-text= <key_and_keystore_password> },implementation-properties={keyAlias= <key_alias> ,external=true,externalPath= <path_to_BCFKS_credential_store> ,keyStoreType=BCFKS},create=true,path= <path_to_keystore> ,modifiable=true, other-providers= <aggregate_provider_name> )
/subsystem=elytron/credential-store=exampleFipsCredentialStore:add(credential-reference={clear-text=password},implementation-properties={keyAlias=exampleKeyAlias,external=true, externalPath=credentialStore.bcfks, keyStoreType=BCFKS}, create=true, path=__<path_to_keystore>__/examplekeystore.bcfks, modifiable=true, other-providers=exampleAggregateProvider)
/subsystem=elytron/credential-store= <credential_store_name> :add-alias(alias= <alias> , secret-value= <secret_value> )
/subsystem=elytron/credential-store=exampleFipsCredentialStore:add-alias(alias=exampleAlias, secret-value=secret)
/subsystem=elytron/credential-store= <credential_store_name> :read-aliases()
/subsystem=elytron/credential-store=exampleFipsCredentialStore:read-aliases() { "outcome" => "success", "result" => ["examplealias"] }
module add --help