#Oauth Scopes0 utenti parlano di questo argomento

We are sending Each user through per user named credentials OAuth Flow programatically one 1st login, Can we intercept this flow send some additional params here ?

We are using custom Auth Plug in class and in this URL navigation to authenticate against per user principle authentication is happening without issue but in the next api calls we are getting 403 from our Backend as this api call is happening with the access token of OAuth User Flow hence apogee is not allowing to go through ,

The expectations is either we should send few other params to OAuth User Flow so user gets correct Access token to use in next actual call

Or In the next api call on 403 we should force access token to expire in apex ,

This is possible ,

Any help would greatly appreciate.

Salesforce - azure ad auth provider + named credentils

• Does Salesforce supports openid connect with azure AD for api access?

Background : We have configured auth provider using openid to connect with azure AD instance but it’s not able to renew access token in exchange with refresh token automatically when access token expires after 1 hr. Any experience handling oauth between SF AND AZURE declaratively using named credential.

Note : offline access and openid have already been defined in the scope along with my api resource scope. #Oauth Scopes #Namedcredential #Azure AD #AuthProviderPluginClass 

Hi Trailblazers,

As a developer, I am responsible to fetch data from multiple organizations that installed a Classic App created by my company. The app was previously set with callback URLs and possibly oauth scopes but currently, we need to update scopes and the callback urls. My questions are:

- Can I update oauth scopes for a classic app (maybe convert it to a connected app)

- Can I change the Callback Url for a Classic App

Thanks for any tips that you guys may have.