We’re using the AWS SaaS connector in SailPoint Identity Security Cloud, and enabling accounts isn’t working.
Issue:
Disable works: ISC disables the account and the IAM user is disabled in AWS.
Enable doesn’t: ISC shows the enable request as Success, but the IAM user stays disabled in AWS.
What we checked: According to the connector documentation (IAM User Status), Enable should set the console password and reactivate the most recently created access keys, CodeCommit credentials and signing certificates. Disable removes the console password and deactivates them.
Since enable needs to set a console password, we added an ENABLE provisioning policy with a password field. After that, the enable operation failed with this error:
[ConnectorError] {ExceptionType=sailpoint.connector.ConnectorException,
LocalizedMessage=java.lang.UnsupportedOperationException:
setPassword not supported by class openconnector.connector.aws.SaasAWSConnector}
First, I would remove the password field from the Enable policy, since that added field is what invokes the unsupported setPassword method. SailPoint documents password on the Create Account policy and documents enable as setting the console password, so enable is not meant to take a password through the provisioning policy.
On enable reporting Success while the IAM user stays disabled: AWS IAM users have no single enable/disable flag, so the connector runs enable as a set of IAM write calls (recreate the login profile, reactivate the last-created access keys, reactivate signing certificates), per the IAM User Status section. A Success status in ISC does not confirm that each of those changes was actually applied in AWS.
Disable working does not prove enable has the permissions it needs. Disable uses iam:DeleteLoginProfile, while restoring console access needs iam:CreateLoginProfile and iam:UpdateLoginProfile, and reactivating keys needs iam:UpdateAccessKey. Those are separate actions in the SaaS connector’s SPProvisioningPolicy, so a role that can disable may still be missing the enable-side permissions.
I would confirm it directly in AWS right after an enable:
aws iam get-login-profile --user-name <user> — NoSuchEntity means the console login profile was not recreated.
aws iam list-access-keys --user-name <user> — check whether the most recently created key is back to Active.
CloudTrail in the target AWS account (IAM is a global service, so its events land in us-east-1) — look for CreateLoginProfile, UpdateLoginProfile and UpdateAccessKey, and any AccessDenied on them. An AccessDenied there indicates an AWS authorization problem (the role policy, an SCP, or a permissions boundary). If the calls are not there at all, confirm you are looking in the right account and region before concluding it is connector-side.
If the permissions are correct but AWS still shows no change, I would turn on connector debug logging and open a Support case.
Hi Ahmed ibrahim,
The setPassword error Cause is clear, The password field you added to the ENABLE provisioning policy makes ISC call setPassword, which the SaasAWSConnector class does not implement UnsupportedOperationException.
Exact fix could be just Delete the password field from the ENABLE provisioning policy and save the source. The error will stop. Password fields belong on Create Account or Change Password operations, not Enable.
Enable shows Success but AWS user stays disabled
it was happening before you added the field. There is no tenant setting that resolves it, you must isolate it:
Remove the password field, then in a sandbox: disable and re-enable a disposable IAM user.
Verify AWS-side permissions on the connector’s cross-account role. Disable only needs iam:DeleteLoginProfile. Enable additionally needs: iam:CreateLoginProfile + iam:UpdateLoginProfile (console password) iam:UpdateAccessKey (reactivate keys)
plus update actions for CodeCommit credentials and signing certificates if used.
Compare your role against SailPoint’s SPProvisioningPolicy. Check for SCPs and permissions boundaries too — an explicit deny there overrides the role policy.
Check CloudTrail in the target account right after the enable:
AccessDenied on CreateLoginProfile/UpdateAccessKey → AWS authorization problem, fix the role/SCP/boundary.
No write events at all, the connector isn’t performing the documented enable → open a SailPoint Support case with the account activity, timestamps, user ARN, and CloudTrail evidence. Ask them to confirm how the connector supplies the enable-time console password, since it’s undocumented.
check AWS Cloud Logs if you have access to view for your app:
Manual way of disabling and Enabling
We are running into this same issue. We are also having issues using Password Management to reset account passwords.
[ConnectorError] {ExceptionType=sailpoint.connector.ConnectorException,
LocalizedMessage=java.lang.UnsupportedOperationException:
setPassword not supported by class openconnector.connector.aws.SaasAWSConnector}
This error message looks like it is an issue with the Sailpoint SAAS connector not having the set-password function. I am opening a ticket.