Salesforce Identity

Hi All,

I am trying to install Identity connect on a windows server 2019. I am facing some issues during setup.bat execution.

It is more related to PostGreSQL connection, but I am not sure what is causing the failure. When I did it on my personal laptop it worked fine, no issues were there.

Below is the error details. Any help on this would be appreciated.

@Samuel Rosen

Hi @Salesforce Identity 

How do I re-authentication third party auth provider after revoke auth provider's account from Third-Party Account Links related list of user object and how can I control permission to revoke auth provider's account at Third-Party Account Links related list of user object?

Regarding the upcoming change "Device Activation for certain Single Sign-On (SSO) user logins" - we have SAML SSO with Azure Entra Id. Azure by default sets AuthnContext to "unspecified" unless SP explicitly requests a specific AuthnContext. How can we set Salesforce to request for example "mfa"?

Hi, I am trying to implement custom registration page with email verification for our experience site, but when I am trying to initiate verification I am getting 'System.NoAccessException : Unable to generate security token'. Can you help me here  to find out what permission I am missing here? #*ExperienceCloudShowMeHow #Self Registration #Salesforce Identity

It's possible to create a "Packaged" ECA and use this directly in the org it's created in and its sandboxes, i.e. never actually packaging this. 

QUESTION: Is this officially supported approach, or any reason not to do this? 

It seems very helpful because:

• The distribution state of "packaged" means this app cascades to sandboxes
• It has benefits over a connected app because the policies (e.g. preauthorised users) exist in the sandbox but are applied for the same client credentials used in production
• There's no pacakging overhead

But it's weird to create a "packaged" app which will never be packaged! Could behaviours supporting this workflow change in future or is it OK to roll out apps to be used in this way? 

Would be great to hear a steer from Salesforce identity folks if possible. Thank you!! 

We are using salesforce as an IDP for multiple external sites. 

The scenario is : 

1. I am on the first external site, I try to log in 
2. The site redirect me to Salesforce (via OIDC) to log in
3. I perform the login at the salesforce level (in a salesforce site with a custom domain like : myCustomDoamin.force.com)
4. I am redirected back to my site authenticated 
5. --------------second part-----------------
6. I am on the second site, I try to log in 
7. The site redirect me to Salesforce (via SAML) to log in
8. I am not logged in in Salesforce, hence I have to re-login at the salesforce level again (in a salesfoce site with a custom domain like : myCustom-Domain.com)

Question : is there any limitation regarding Sites custom domain and SSO ? 

Thanks in advance,

Hello 

I am trying to create a unified login experience for community users and have set up an openid auth provider.  After navingating to url i successfully go to idp login page, then click 'allow' to grant salesforce access, then get that error "We can't log you in because of an authentication error" (ErrorCode=No_Oauth_Token&ErrorDescription=Empty+Response).  

The idp team checked the metrics at their end  and mentioned that it seems to fail after they pass back to us with authorization code but before it is exchanged.  

What is missing, and what logs or details can i check to figure this out? 

Hello, 

I am trying to understand  the passwordless login  process for community users, 

allowing them to connect with an OTP received by SMS or email. 

I looked at many of the Salesforce pages / documentation  but i am lost. 

Is an experience cloud  site running considered a public or private client ?  

Is there any article available on the net explaining the process / constraint ? 

Regards 

Jerome