0

The session expiry for an accessToken can be configured at org level, profile level, connected app level. When authenticating via private key certificate using the JWT OAuth Flow, which session expiry is considered?

We are experiencing a strange behaviour: we authenticate using the sfdx-cli and we use the token often, so we would expect it not to expiry. However, after few months it expires anyways

Improve this question
1
  • 1
    I had something similar happen to me, took me a minute to realise it was during a Salesforce release. Different use case but if the timelines match... – Girbot Feb 23 at 15:52
0

The precedence here is:
connected app > profile > org-wide

Improve this answer
2
  • When the connected app is empty it goes on profile? – Edmondo1984 Feb 23 at 15:43
  • Yes. It takes the value of whatever level that information is defined at, in order of precedence. If not defined on the connected app, it'll look to see if it's defined at the profile level. If it's not defined there either, it'll use the org-wide value. – Derek F Feb 23 at 15:50

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service, privacy policy and cookie policy

Not the answer you're looking for? Browse other questions tagged or ask your own question.