Skip to main content

#Identity & Access Management토론 중인 항목 0개

Hello everyone,

For those working on the Get Hands-on with Data Cloud trai

l in Trailhead, please make sure to follow these steps: 

 

  1. Create a Data Cloud playground.
  2. Complete all the tasks in the trail before the playground expires.
  3. Once finished, you’ll complete the Data Cloud trail.
  4. By following these steps, you should not encounter errors with the Identity Resolution Ruleset task module.

Hope this helps! Best of luck, and happy learning! 🔥🚀 

 

#Data Cloud  #DataQuality  #Identity & Access Management

0/9000

Hi Trailblazers,

 

I need to create a restriction rule to restrict records based on some criteria and restrict for particular profile but I'm unable to select the profile name in restriction rules

 

There is no option to select profile name instead they have an option to select ProfileId.

 

Anyone knows how to do with restriction rules with profile name? 

 

#Restriction Rules  #Identity & Access Management

댓글 1개
  1. 2025년 7월 10일 오후 1:58

    Hi @Sahil Jain

     

    The "Permission Criteria" type is designed to be related to Custom Permissions only, therefore you cannot directly select a Profile.  

     

    In order to do what you want, you should first create a Custom Permission and assign it to the desired Profile. Then select your Custom Permission with operator equals true. This means that any user that has the custom permission (should it be from his profile or any Permission Set that has the custom permission) will benefit from the Restriction Rule.

0/9000

Hi, 

 

I am trying to set up a common identity community for a customer where they can login and access other SF apps(customer - communities). 

 

Let's say one community is called identity and the other is called customer. I have followed the below steps.

  1. I have enabled Identity Provider. 
  2. I have created the Single Sign On Settings using the metadata url for the identity community IDP that was generated by Salesforce. 
  3. I have created the Connected App to let the Identity provider(identity community)  know about the Service Provider(customer community)
  4. I have created a permission set that is tied to the connectedApp and is assigned to an individual. 
  5. Set up login mechanism for the community as set up in single sign on settings.
  6. I go to Home page or customer community <domain>/customer
  7. I get routed to the login page of the identity <domain>/identity/login
  8. After I login with a username and password, I am getting stuck in a LOOP, where the browser goes to the identity --> customer-->identity over and over again. 
  9. If I add another login mechanism for the community then the LOOP stops itself after a few tried and takes me back to the login page of the customer community. 

The user login history shows that they have logged in successfully. 

The Identity Provider Event Log shows a successful login. 

 

Has anyone experienced this? What am I doing wrong?

 

 @Ian Glazer Can someone from you team help?

 

Cheers, Gaurav

#Identity & Access Management #Experience Cloud

답변 2개
0/9000

Hi all,

 

I have a requirement where we are integrating Salesforce with an external system. It is a 1-way communication where SF will use their API to pull in the necessary data. For authorization purpose they are using oAuth 2.0 Client Credentials with certificate (Microsoft oAuth link). They have provided us with the following information

1. Client ID

2. Tenant ID

3. .pfx certificate

4. Token Endpoint

5. scope

6. app endpoint.

 

I have tried a couple of ways using named credentials, but not able to establish the connection.

 

I would highly appreciate any help here on how to achieve this using salesforce. 

Thank you,

Aiswarya

 

#Identity & Access Management #Salesforce Developer #Named Credentials #Integration #TrailblazerCommunity #Advanced Administrator

답변 5개
  1. 2024년 3월 1일 오후 8:21

    Steps taken so far:

    1. Converted .pfx certificate into JKS keystore file using openssl as pfx file format is not compatible with salesforce

    2. Uploaded the certificate into the client and key management setup

    3. Created an external credential with authentication protocol type as Client credentials with JWT assertion.

    4. Configured the JWT claims.

    5. Created a named credential and linked it with the external credential.

    6. Apex code snippet to test the connection.

    7. The response received was status code = 403 which indicates the credentials we are sending are wrong.

     

    Microsoft requires the following information in request body to authenticate.

    1. Client_assertion_type : available

    2. Grant_type - available

    3. Client_assertion - NOT AVAILABLE

    4. Scope - available

    5. Tenant - available

    6. Client_id - available

     

    The main questions are:

    1. does Salesforce generate the client_assertion and send it in the request or do we need to generate it?

    2. If we need to generate, what is the way to do this in Salesforce or Apex?

     

    #Integration #Salesforce Developer #Identity & Access Management #Named Credentials #Advanced Administrator #TrailblazerCommunity

0/9000

We have enforced SSO for our users. When a user authenticates with Salesforce using an external application such as workbench or a google sheet connector they login using the custom domain and Microsoft Azure SSO login button.

 

The login history suggests differently, and says they are logging in using 'login.salesforce.com'. For such a login I would expect to see our custom domain.

 

Here are the logins highlighted in green where I would expect to the login URL as the custom domain

 

Am i misunderstanding the login history?

 

 

#Security #Identity & Access Management #SSO

답변 1개
0/9000
Dilipan M (Equiniti) 님이 #SSO에 질문했습니다

My single sign on shows two different expiration date.

When I checked the SAML Single Sign On settings page in setup, for the field 'Identity Provider Certificate', It shows the following value 'CN=Microsoft Azure Federated SSO Certificate

Expiration: 4 Jul 2026 13:10:37 GMT'

 

I then opened the certificate itself, present on the field Request Signing Certificate, it says that the expiration date is in 2024.

 

Which is the true expiration date?

 

I checked with my Identity Provider team, they said it is 2026, but want to double check why it is showing 2024 in SF.

 

#SSO  #SSO Setup  #Single Sing-on  #Security  #Identity & Access Management

답변 1개
  1. Sushil Kumar (UKG) Forum Ambassador
    2024년 2월 21일 오전 11:23
    Those are two different types of certificate. Request signing certificate could be used by your IDP to verify the Auth N request coming from Service provider (which is Salesforce in this case). A lot of cases IDP may not verify this certificate. You can check with your IDP team if they use SF request signing certificate for auth N request(For SP initiated SSO). The second certificate is the IDP certificate which is provided by your IDP, when IDP posts SAML response, they sign response with that certificate, and then Salesforce can use certificate uploaded in SF to verify the response to make sure it’s coming from right source.
0/9000

As per new OAuth 2.0 Hybrid App flow, Salesforce returns necessary cookie names, session ids, and domain details in the response so that when app opens the web view it can directly use the session id set in the cookies and grant access to the Salesforce pages inside the App.

 

Reference :

https://help.salesforce.com/s/articleView?id=sf.remoteaccess_oauth_hybrid_app_flow_cookies.htm&type=5

 

However I was wondering whether we can set cookies on other domains than the "current" native app domain due to security reasons?

 

#OAuth 2.0 #Hybrid #Identity & Access Management

0/9000

On Wednesday, Salesforce Architects of Jacksonville Florida had a great meeting at The Link in Nocatee.

 

Mahesh Somineni presented to a hybrid group about Salesforce Identity Flows.

 

It was a great session of theory mixed with practical Postman demos.

 

Watch the full YouTube video below. Check the resources Mahesh graciously shared in the video description.

 

Thanks to The Link, for providing the meeting space.

 

https://youtu.be/jqS0Wf8E_R4?si=BwAuOTLhc2Ndg_yE

 

#Technical Architect #Integration Architect #Identity & Access Management

댓글 2개
0/9000
댓글 6개
  1. 2023년 9월 26일 오전 1:10

    I will be there as soon as I can, taking my car for an oil change, so depending on how long they take, I might be a little bit late.  Looking forward to this talk!

0/9000

Hi Architects, 

I am trying to implement Oauth 2.0 Asset Token Flow using Postman. But cannot understand how actually can I use Asset Token to create/update records in salesforce. Here is what is did, 

 

  1. Got an Access token using Web Server Flow (Postman)
  2. Created a unsigned JWT for Actor Token. 
  3. Exchanged Actor Token & Access Token to Asset Token (Postman)
    1. In this step I was also able to create a new Asset (which actually registers an Asset based on documentation.)
  4. But I cannot access any API using this Asset token. 

How to use the Asset Token?. Any code sample or use cases will be appreciated.

#Identity & Access Management #OAuth 2.0

Thanks in advance

Prosenjit Sarkar

답변 3개
  1. 2023년 8월 7일 오전 8:54

    Hi @Prosenjit Sarkar - Asset tokens in Salesforce are not designed for API calls. Instead, the backend service validates the asset token's legitimacy to determine if the device is authorized for the specific action. When it comes to API calls, particularly for CRUD operations, using bearer tokens is the recommended approach.

     

    https://help.salesforce.com/s/articleView?language=en_US&id=sf.remoteaccess_asset_token_using_validating.htm&type=5

0/9000