Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Could not fetch JWT bearer token for service of type xsuaa #5334

Open
infosail opened this issue Jan 3, 2025 · 2 comments
Open

Could not fetch JWT bearer token for service of type xsuaa #5334

infosail opened this issue Jan 3, 2025 · 2 comments
Labels
bug Something isn't working

Comments

@infosail
Copy link

infosail commented Jan 3, 2025

Describe the Bug

After the cloud-sdk upgrade (3.11.0 -> 3.20.0), our code (see below) throws an error "Could not fetch JWT bearer token for service of type xsuaa: HTTP request [XsuaaService.fetchJwtBearerToken] to https://appgyver-eu10-subscription-provider.authentication.cert.eu10.hana.ondemand.com/oauth/token timed out after 2000 ms.
at /app/node_modules/@sap-cloud-sdk/connectivity/dist/scp-cf/xsuaa-service.js:77:15" in one customer's account. This error occurs randomly and seems account specific.

Steps to Reproduce

getDestinationFromDestinationService({
      destinationName,
      jwt: retrieveJwt(req),
      iasToXsuaaTokenExchange: true,
      useCache,
      selectionStrategy: alwaysSubscriber,
    });

Expected Behavior

The fetchJwtBearerToken() always return user token successfully.

Screenshots

No response

Used Versions

  • Node version: 16.14.0
  • NPM version: 8.3.1
  • SAP Cloud SDK version: 3.20.0

Code Examples

No response

Log File

No response

Affected Development Phase

Production

Impact

Blocked

Timeline

The customer complained that their work is halted due to the error in view of their tight schedule.

Additional Context

No response

@infosail infosail added the bug Something isn't working label Jan 3, 2025
@infosail
Copy link
Author

infosail commented Jan 10, 2025

The error does not occur in the customer's Sydney subaccount but in the Frankfurt subaccount.
Image

The customer subscribed our service, which calls Cloud SDK internally, into his subaccounts.

@KavithaSiva
Copy link
Contributor

Hi @infosail,

Apologies for not answering earlier, we seemed to have missed this issue.
Does the issue still persist?
As you mentioned that this is sub-account specific, we have doubts if this issue is related to Cloud SDK, we think it could be a setup issue.
Could you please attach debug logs for when the error occurs, this would enable us to check further.

Regards,
Kavitha

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

2 participants