API Auth2.0 in seperate window -
Posted: Wed Feb 21, 2024 5:50 am
Hello,
When creating and authorisation via Auth2.0 their is a pop up window, and the redirect has a different URi
Type: Authorisation Code
Authentication URL: https://<client_ID>.simprosuite.com/oauth2/login?client_id=xxxxxxxxxxxxxxxxxx
Redirect URL: /oauth2/accessCode
Token URL: https://<client_ID>.simprosuite.com/oauth2/token
client_id: xxxxxxxxxxxxxx
client_secret: xxxxxxxxxxxx
grant_type: authorization_code
The authorisation hangs as the URi is not pointing in the right redirect to extract the code
https://<client_ID>.simprosuite.com/oauth2/auth?%3Fredirect_uri=https%3A%2F%2Fwww.integromat.com%2Foauth%2Fcb%2Foauth2&state=xxxxxxxxxxxxxx&client_id=xxxxxxxxxxxxxx&response_type=code&grant_type=authorization_code&code=%2Foauth2%2FaccessCode
https://<client_ID>.simprosuite.com/oauth2/accessCode?code=xxxxxxxxxxxxxx&state=xxxxxxxxxxx
I beleive the resolution is in the access token parameters of the advanced settings, when performing these API calls, is it the suggestion that a top level user be the primary login, as others may leave and the access would then need to be reattained.
Note: XXXXX where sensitive content is also
When creating and authorisation via Auth2.0 their is a pop up window, and the redirect has a different URi
Type: Authorisation Code
Authentication URL: https://<client_ID>.simprosuite.com/oauth2/login?client_id=xxxxxxxxxxxxxxxxxx
Redirect URL: /oauth2/accessCode
Token URL: https://<client_ID>.simprosuite.com/oauth2/token
client_id: xxxxxxxxxxxxxx
client_secret: xxxxxxxxxxxx
grant_type: authorization_code
The authorisation hangs as the URi is not pointing in the right redirect to extract the code
https://<client_ID>.simprosuite.com/oauth2/auth?%3Fredirect_uri=https%3A%2F%2Fwww.integromat.com%2Foauth%2Fcb%2Foauth2&state=xxxxxxxxxxxxxx&client_id=xxxxxxxxxxxxxx&response_type=code&grant_type=authorization_code&code=%2Foauth2%2FaccessCode
https://<client_ID>.simprosuite.com/oauth2/accessCode?code=xxxxxxxxxxxxxx&state=xxxxxxxxxxx
I beleive the resolution is in the access token parameters of the advanced settings, when performing these API calls, is it the suggestion that a top level user be the primary login, as others may leave and the access would then need to be reattained.
Note: XXXXX where sensitive content is also