Question

Evoke Technologies
US
Last activity: 28 Aug 2025 11:43 EDT
Certificate-based JSON Web Token authentication scheme For SharePoint REST APIs
Hi Pega Community,
I'm experiencing multiple issues with SharePoint Online Integration in Pega and would appreciate your guidance on resolving them.
Issues Encountered:
1. OAuth2 Client Creation Failures:
- Getting error: "Caught Exception while creating OAuth2 client - Unable to obtain access token for client details in authentication profile configured for connector"
- Access token endpoint invocation fails with: "Response status: 400 Bad Request, statuscode=400"
- This occurs despite having correct client credentials and token endpoint configuration which works from postman.
2. JWT Token Profile Configuration Problems:
- Created a new JWT token profile but the system continues to use old cached values instead of my configured claim mappings
- Token profile preview shows outdated information despite saving changes multiple times
- Claims are not being mapped correctly - receiving original JWT claims instead of mapped values
- Tried using this JWT from postman and the API does work but trying the same configuration in pega Fails.
3. 401 Unauthorized Errors:
Hi Pega Community,
I'm experiencing multiple issues with SharePoint Online Integration in Pega and would appreciate your guidance on resolving them.
Issues Encountered:
1. OAuth2 Client Creation Failures:
- Getting error: "Caught Exception while creating OAuth2 client - Unable to obtain access token for client details in authentication profile configured for connector"
- Access token endpoint invocation fails with: "Response status: 400 Bad Request, statuscode=400"
- This occurs despite having correct client credentials and token endpoint configuration which works from postman.
2. JWT Token Profile Configuration Problems:
- Created a new JWT token profile but the system continues to use old cached values instead of my configured claim mappings
- Token profile preview shows outdated information despite saving changes multiple times
- Claims are not being mapped correctly - receiving original JWT claims instead of mapped values
- Tried using this JWT from postman and the API does work but trying the same configuration in pega Fails.
3. 401 Unauthorized Errors:
- Authentication appears to complete successfully but subsequent API calls fail
- Getting access denied errors when attempting SharePoint operations
- Token seems to be generated but lacks proper authorization for SharePoint resources
5. Token Caching Problems:
- Token profile changes not reflecting in runtime
- System continues to use cached/old token configurations
- Preview functionality shows stale data despite configuration updates
Environment:
- Pega Platform: 24.2
- Integration: SharePoint Online via REST APIs
- Authentication: OAuth2 with JWT tokens
- Microsoft Azure App Registration
Current Status: The integration was working previously for existing APIS but started failing when we tried to configure a new API, possibly related to Microsoft's ongoing Azure security updates and ACS authentication deprecation.
Has anyone encountered similar OAuth2 and token profile issues with Microsoft integrations? Any guidance on resolving these authentication and configuration problems would be greatly appreciated.
Thanks in advance!
Roshan Raj A K