Skip to main content
Solved

When using sharepoint package, having an error as credentials couldnt be found in credential vault. How to solve it?

  • September 3, 2025
  • 7 replies
  • 80 views

Forum|alt.badge.img+12

In dev, it works. In prod i was having “access is denied” error. After sharepoint auth connection token was activated, i started to have "credentials couldnt be found in credential vault” Why is that? How to solve it?

Best answer by Semih 3318

@Shreya.Kumar  the answer is the sharepoint authentication must be refreshed by the user’s controlroom whoever wants to use it.
Since i was not admin of the vdi, i thought it was being authenticated by global team. But when i refreshed token and activated it, started to work expectedly

7 replies

Padmakumar
Premier Pathfinder | Tier 7
Forum|alt.badge.img+15
  • Premier Pathfinder | Tier 7
  • September 3, 2025

Hi ​@Semih 3318,

 

Make sure that your Runner user is the Consumer of the Credential vault in order to use the credentials. 

If the Consumer role is missing, then the credentials won't be accessible by the runner user.


Forum|alt.badge.img+12
  • Author
  • Pathfinder Advocate | Tier 6
  • September 3, 2025

@Padmakumar i dont understand. Because sharepoint package  only needs Authenticate step. And its only about OAuth connection. ProviderType-Connectionname-Token type
where are credentials? there is no credential or consumer here as i know


Padmakumar
Premier Pathfinder | Tier 7
Forum|alt.badge.img+15
  • Premier Pathfinder | Tier 7
  • September 3, 2025

@Padmakumar i dont understand. Because sharepoint package  only needs Authenticate step. And its only about OAuth connection. ProviderType-Connectionname-Token type
where are credentials? there is no credential or consumer here as i know

 

Credential can be anything. Like Username& Password, Access token, API Key etc.

In your case, the Token must be the credential that the bot is trying to retrieve from the vault. In the Dev environment, the runner must have access to the same, which is why the execution is working there. 

Whereas in Prod, the access is missing, due to which the execution is failing. So, as I have mentioned, you need to provide Consumer role to your Bot runner user to access the Credentials (Token).

 

 

There is one more possibility here, which is that the Vault or Credential itself is missing. In this case, you need to create the same one similar to your Dev instance.


Shreya.Kumar
Pathfinder Community Team
Forum|alt.badge.img+14
  • Pathfinder Community Team
  • October 7, 2025

@Semih 3318 if Padmakumar helped you solve the issue, please mark it as best answer!


Forum|alt.badge.img+12
  • Author
  • Pathfinder Advocate | Tier 6
  • Answer
  • October 7, 2025

@Shreya.Kumar  the answer is the sharepoint authentication must be refreshed by the user’s controlroom whoever wants to use it.
Since i was not admin of the vdi, i thought it was being authenticated by global team. But when i refreshed token and activated it, started to work expectedly


Forum|alt.badge.img+1
  • Cadet | Tier 2
  • December 3, 2025

Hi ​@Shreya.Kumar,

I am facing similar error(credentials couldn’t be found in credential vault), however here I’m get this error message only when I use Authenticate action with User-Specific configuration. And it’s working fine upon using Shared configuration within the Authenticate action.

Can you please let me know why it’s not working with User-Specific token type?

I have mentioned below my configurations.

  1. Save login credentials(checkbox) is not selected, as I don’t want  to have a shared token.
  1. SharePoint package > Authenticate action > Token type: User-specific
  1. Error message:

 


Padmakumar
Premier Pathfinder | Tier 7
Forum|alt.badge.img+15
  • Premier Pathfinder | Tier 7
  • December 3, 2025

Hi ​@Shreya.Kumar,

I am facing similar error(credentials couldn’t be found in credential vault), however here I’m get this error message only when I use Authenticate action with User-Specific configuration. And it’s working fine upon using Shared configuration within the Authenticate action.

Can you please let me know why it’s not working with User-Specific token type?

I have mentioned below my configurations.

  1. Save login credentials(checkbox) is not selected, as I don’t want  to have a shared token.
  1. SharePoint package > Authenticate action > Token type: User-specific
  1. Error message:

 

Hi ​@Sunil 9849,

 

As per the error message, the bot is unable to retrieve the credential from the vault. Please check the accessibility of the same from your runner device or check whether it has the consumer permission of the respective locker.