Announcing the Saviynt Knowledge Exchange unifying the Saviynt forums, documentation, training,
and more in a single search tool across platforms. Read the announcement here.

Schema upload based Accounts import

Amar_Simha
Regular Contributor
Regular Contributor

Hi Team,

We are on using the schema upload jobs for accounts import , there is a scenario where the username is not available at application side and only have email ID. Can we pass email ID in email as a column and it will map the account to the user based on the email match? 

Is that a possible option, the attribute might also be employeeID. But both these are not same as username in Saviynt.

Please share your views.

17 REPLIES 17

naveenss
All-Star
All-Star

Hi @Amar_Simha ,

Yes this is possible by configuring the user-account correlation in Saviynt. However, the account will be mapped to the user in Saviynt ONLY if there is a matching user identity found in Saviynt based on the email address.

Either it is email, employeeID or any other attribute, there should be a user identity matching the record from your account import file.

Please let me know if this helps!

 

Regards,
Naveen Sakleshpur
If this reply answered your question, please click the Accept As Solution button to help future users who may have a similar problem.

Amar_Simha
Regular Contributor
Regular Contributor

Thanks @naveenss & @AmitM for the update. Just to clarify, we are performing CSV file uploads, will the correlation rule be effective in that case? as this is disconnected system. Please confirm.

@Amar_Simha  Yes the correlation rule will trigger in this case as well.

 

Regards,
Naveen Sakleshpur
If this reply answered your question, please click the Accept As Solution button to help future users who may have a similar problem.

Amar_Simha
Regular Contributor
Regular Contributor

Thanks @naveenss , let me try and confirm.

AmitM
Valued Contributor
Valued Contributor

Hi @Amar_Simha , Please refer this doc https://docs.saviyntcloud.com/bundle/EIC-Admin-v24x/page/Content/Chapter02-Identity-Repository/Viewi...

Search User Account Correlation Rule

You can use multiple conditions OR / AND and compare multiple and different account attributes vs user attributes.

User Account Correlation Rule

Specify this rule to map users in EIC with the accounts during import. This rule is configured by the application owner. To create rules, use Basic Config or Advanced Config buttons. By default, the Basic Config view is displayed. You can edit or delete a rule.

To create rule using the Basic Config option, perform the following steps:

  1. In the Rules window, select a user attribute under Users.

  2. Specify the number of characters to use from the selected user attribute under InitialChar.

  3. [Optional] To add an additional condition, click + under Action.

  4. Select an account attribute from Accounts.

  5. [Optional] To add optional rules such as Rule-2, Rule-3, click Add Rule.
    If the Rule-1 condition fails due to any reason, the optional rule is applied to the user account correlation rule.
    For instance, Rule-1: firstname (3) + lastname (2)
    OR
    Rule-2: firstname (1) + displayname (3)+lastname (2)
    If multiple rules are defined, they are separated by # in the database to signify the start of the subsequent rule.

  6. Click Save to save the rule.

To create a rule using the Advanced Config option, perform the following steps:

  1. In the Ruleswindow, select Advanced Config.

  2. Specify the query under SQL Query. Special characters are supported in the query.

    Note

    Querying only for attributes in the users and accountstables of the database is supported.

    Sample query: case when (users.employeetype = 'Contractor') THEN concat ('C-', users.username) ELSE users.username END

  3. Click Save to save the rule.

Thanks,

Amit

If this answers your query, Please ACCEPT SOLUTION and give KUDOS.

rushikeshvartak
All-Star
All-Star

You can have multiple correlation rules in Endpoint - User Account Correlation. It get applied when account is imported via job or via file.

 

rushikeshvartak_0-1708664706135.png

 


Regards,
Rushikesh Vartak
If you find the response useful, kindly consider selecting Accept As Solution and clicking on the kudos button.

Amar_Simha
Regular Contributor
Regular Contributor

@rushikeshvartak @naveenss @AmitM - thank for the updates, we are able to use corelation rules via file import.

just one clarification, we are trying to use one of the custom property as correlation rule and application team is not comfortable using custom property as column name as they do no follow such naming pattern and would want to send the column they have as input.

I wanted to check if it is possible that attribute mapping can be done for file import using schema jobs like we do for connected applications? Like application want to send the column name they have but we would want to map to one of custom property on Saviynt side and use the same as correlation rule to map accounts to users.

Please let me know the feasibility on this. Thanks!

You need to define customproperty. Application team can't define from column values should be consider.


Regards,
Rushikesh Vartak
If you find the response useful, kindly consider selecting Accept As Solution and clicking on the kudos button.

Amar_Simha
Regular Contributor
Regular Contributor

@rushikeshvartak : Thanks for the update. But, I did not fully understand the response. You mean to say that this use case is not possible?

If you could re-share your response with an example that would be helpful.

Amar_Simha
Regular Contributor
Regular Contributor

@rushikeshvartak @naveenss @AmitM : Can you please check and share your views on the use case.

We are running on some tight timelines and appreciate if you can share possible options for the same.

AmitM
Valued Contributor
Valued Contributor

Hi @Amar_Simha , if I have understood your ask correctly. Your application team is generating this file and they don't want to use CP's format and instead use more user friendly column names. That they have been using in past.

That is not supported AFAIK and you have to use CPs name only in Schema upload. So if they dont want to give you in that format, you / Saviynt admins has to convert their file into Saviynt supported format.

Thanks,

Amit

If this answers your query, Please ACCEPT SOLUTION and give KUDOS.

Hi @Amar_Simha ,

Yes this can be done. Please see the attached format. Irrespective of the column names provided by the app team, ignore the first line in your data file. However, keep in mind to setup the correct account attributes in the SAV file. Let me know if you have any questions. 

Note: Change the format to .sav from .txt file from the attachment. 

 

 

Regards,
Naveen Sakleshpur
If this reply answered your question, please click the Accept As Solution button to help future users who may have a similar problem.

Amar_Simha
Regular Contributor
Regular Contributor

Thank you @naveenss, I am trying the said option.

Just wanted to check, if this works only for CPs or another column names like accountname, endpointname etc.

@Amar_Simha  this works on all account properties.

 

Regards,
Naveen Sakleshpur
If this reply answered your question, please click the Accept As Solution button to help future users who may have a similar problem.

Amar_Simha
Regular Contributor
Regular Contributor

Thanks @naveenss for your inputs. It is working fine for accounts import.

I would assume this works the same way for entitlement import through Schema Entitlement job? Please confirm.

@Amar_Simha  yes, It should ideally work the same for entitlement import as well. 

 

Regards,
Naveen Sakleshpur
If this reply answered your question, please click the Accept As Solution button to help future users who may have a similar problem.

Dave
Community Manager
Community Manager

Hi @Amar_Simha - Be sure to click the "Accept As Solution" button on each reply (or replies) that best answered your original question.  You can also click the "Kudos" button to give thanks on other replies that provided helpful information. Thank you! 

Solution.JPG