How to bring back missing Object KeyStorePassword from SCIM Config safe

cancel
Showing results for 
Show  only  | Search instead for 
Did you mean: 
Announcements

Welcome Idira to LIVEcommunity!

Our community just got stronger! Explore new identity security resources, connect with experts, and discover more ways to learn and collaborate.

Meet Idira

How to bring back missing Object KeyStorePassword from SCIM Config safe

L3 Networker

While I was executing SCIM Server v1.3.5 install which I believe went fine without encountering any errors, I came to a point to start SCIM server manually.

Field_Content_versions_oct20__068Vy00000Fo6eNIAR.pngOnce I started up SCIM server from powershell as an administrator, I ran into an following error.

 

Field_Content_versions_oct20__068Vy00000FoVG6IAN.pngIt turned out KeyStorePassword object is missing from SCIM Config safe which I confirmed it is missing from the Vault server by looking into the contents of that safe.

 

However, looking back a few steps from the install guide, which is step 4 verification, it asked me to check the contents of that safe. It has all the objects expected but it doesn't say KeyStorePassword so I am not sure when this object should be created and by whom/process.

 

Field_Content_versions_oct20__068Vy00000FoZemIAF.png 

 

My question is, is there a way to create and add it to the safe? I am not sure at what stage this file is created.

 

I appreciate your advice and sharing experience with me.

 

 

1 accepted solution

Accepted Solutions

L3 Networker

I was not able to start up SCIM server but following below steps fixed it. Now I am able to access swagger page.

 

  1. create KeyStorePassword object inside of SCIM-Config safe.
  2. my first screenshot, if you read it, there are two problems combined. SCIM-user is failing to read System safe. When I ran into this problem, I did not create Creds file for SCIM-user but later I corrected it AND on top of it, SCIM-user should be the owner of the System safe.
  3. last is SCIM-account password, SCIM-User password and SCIM-user.cred password, they must match it sounds like. Initially, I only allowed SCIM-User password and SCIM-User.cred password to match. That is how I interpreted the implementation guide but my co-worker gave a try to match all three and that did the trick. I was able to access swagger page exposed by SCIM server.

View solution in original post

5 REPLIES 5

L3 Networker

I'm sorry this thread is not an answer but want to add more information.

 

1) There is a step 4.2.2 New SCIM PACLI internal authentication methods to the digital Vault. I initially skipped it thinking it is not necessary however I changed my mind to ran it. SCIM-user.cred and SCIM-user.cred.entropy files are created and I moved them to a right folder. Afterward, I restarted the server and attempted to start up SCIM server. I still got KeyStorePassword object missing however I didn't get sailpoint Exception. Plz refer to the screenshot.

 

Field_Content_versions_oct20__068Vy00000Fp76xIAB.png 

L6 Presenter

Hello!

 

If the keystore is created and the config.yml has the path to it and the password, then through PrivateArk Client you can check the 'SCIM Config' safe to see if a password object called KeyStorePassword is present. If not, create it manually. Name will be KeyStorePassword, it should be in the root folder of the safe, and the value should be the password value that was set for the keystore on the SCIM server.

thanks! Co-worker of mine created manually and that did the trick to get rid of that error. Your answer aligned with his idea exactly.

L3 Networker

I was not able to start up SCIM server but following below steps fixed it. Now I am able to access swagger page.

 

  1. create KeyStorePassword object inside of SCIM-Config safe.
  2. my first screenshot, if you read it, there are two problems combined. SCIM-user is failing to read System safe. When I ran into this problem, I did not create Creds file for SCIM-user but later I corrected it AND on top of it, SCIM-user should be the owner of the System safe.
  3. last is SCIM-account password, SCIM-User password and SCIM-user.cred password, they must match it sounds like. Initially, I only allowed SCIM-User password and SCIM-User.cred password to match. That is how I interpreted the implementation guide but my co-worker gave a try to match all three and that did the trick. I was able to access swagger page exposed by SCIM server.

Super glad to hear that it's working now! Appreciate you outlining the steps that were needed to rectify it as well.

  • 1 accepted solution
  • 158 Views
  • 5 replies
  • 0 Likes
Like what you see?

Show your appreciation!

Click Like if a post is helpful to you or if you just want to show your support.

Click Accept as Solution to acknowledge that the answer to your question has been provided.

The button appears next to the replies on topics you’ve started. The member who gave the solution and all future visitors to this topic will appreciate it!

These simple actions take just seconds of your time, but go a long way in showing appreciation for community members and the LIVEcommunity as a whole!

The LIVEcommunity thanks you for your participation!