Closed (fixed)
Project:
Salesforce Suite
Version:
5.0.x-dev
Component:
salesforce_jwt.module
Priority:
Normal
Category:
Feature request
Assigned:
Unassigned
Reporter:
Created:
24 May 2019 at 22:10 UTC
Updated:
11 Oct 2021 at 16:39 UTC
Jump to comment: Most recent, Most recent file
Comments
Comment #2
jidrone commentedHere is the patch.
Comment #3
aaronbaumanThis article suggests that the login and token urls don't necessarily need to be different: https://help.salesforce.com/articleView?id=000229902&type=1
Only that they need to not be login.salesforce or test.salesforce
Can you test by switching the login URL only?
Comment #4
aaronbaumanComment #5
lostkangaroo commentedI am able to confirm that this is indeed an issue with Gov Cloud. While I don't believe a new plugin and consumer is needed, there does need to be a separation of the login URL being used as both the login endpoint and the audience field as is the case in the existing JWT implementation. This would be simpler to add the token URL as an optional form field and default to the login URL if not provided as would be the case for 99% of users.
As for the concern in #3, the article was updated on Jul 21, 2020, to reflect that users are not able to use login.salesforce.com or test.salesforce.com for login URLs. They are however needed as audience fields for the JWT token itself.
I have tested the above patch and it indeed does the job of allowing connections to Gov Cloud instances.
Comment #7
aaronbaumanGreat, committed to 5.x and 4.x.
Thanks for your patches and patience