Epic Password Attribute for ISC IdentityNow

We have successfully built and connected another EPIC EMP source. We are able to successfully provision an account however we are not sure how to pass along a password to the EPIC EMP account from SailPoint. We have tried modifying the create account section in our source by adding attributes called “password” and “ExternalIdentifier_password_1” but it still does not work. Please see attached screenshots in EPIC of the password field value we are trying to populate with SailPoint.

While we already have another EPIC EMP source that works based on login with AD account, this particular setup of EPIC is provisioning accounts is without using Active Directory accounts. These are EPIC accounts provisioned so that a user can directly login to Epic without an AD account. If I enter a password manually in their Epic account, it works, but as mentioned we are trying to make SailPoint provision the password as well when creating the epic account.

We found the below Sailpoint Healthcare Connector Guide attributes for password but none worked.

password
ExternalIdentifier_password_0
ExternalIdentifier_password_1
Authpassword

We also found this in our VS code for the source but not sure if something needs to be set for password policy for password to be passed.

“passwordPolicies”: null,
“features”: [
“GROUP_PROVISIONING”,
“SEARCH”,
“PROVISIONING”,
“PASSWORD”,
“ENABLE”,
“SYNC_PROVISIONING”,
“UNLOCK”
],

We are nearly successful but just missing this piece to the puzzle. Any help or suggestions is greatly appreciated

Thank you,

@shasap
I dont see “CURRENT_PASSWORD”, “AUTHENTICATE”

I haven’t done integration with ISC but with IIQ, I remember using Password field to set the password. I do remember I added logic like if the user has AD account, then don’t set the password else set it.

Do you know the name of the attribute I need to add in Create Account that would pass the password when it provisions a new account in EPIC?

It should be the “password” attribute. It is definitely NOT the External_identifier_password_0 or any of those. There is a seperate API call for setting a user password, it is not part of either UpdateUser nor CreateUser SOAP endpoints. So it depends on what is implemented in the connector.

I always use the AD Passthru so never tried setting the password directly.

This topic was automatically closed 60 days after the last reply. New replies are no longer allowed.