Share all details about your problem, including any error messages you may have received.
i am trying to enable the sailpoint iiq in login configuration using SAML Based Single Sign-On (SSO)and after configuration when i click to save it it gives me error (Specified attribute is not between the expected values of 1 and 1.)
As per the error, I see there is a lock file in a particular location. Try deleting that file and perform the operation again.
java.nio.file.AccessDeniedException: E:\tomcat\webapps\identityiq\WEB-INF\BundleManagedAttributeIndex\write.lock
at sun.nio.fs.WindowsException.translateToIOException(WindowsException.java:89) ~[?:?]
at sun.nio.fs.WindowsException.rethrowAsIOException(WindowsException.java:103) ~[?:?]
at sun.nio.fs.WindowsException.rethrowAsIOException(WindowsException.java:108) ~[?:?]
at sun.nio.fs.WindowsFileSystemProvider.newFileChannel(WindowsFileSystemProvider.java:120) ~[?:?]
at java.nio.channels.FileChannel.open(FileChannel.java:292) ~[?:?]
at java.nio.channels.FileChannel.open(FileChannel.java:345) ~[?:?]
Although i ensure from the user permissions (has the full control), still have the same error while trying to save the SAML SSO configuration (Specified attribute is not between the expected values of 1 and 1.)
and this is the content of sailpoint log file :
i disable the Rule Based Single Sign-On (SSO) and Enable SAML Based Single Sign-On (SSO)
and this is the SAML Correlation Rule:
// Imports
import sailpoint.object.Identity;
// Making a BIG assumption here that the nameid-format is unspecified/persitent
// Get the nameId from the assertionAttributes
String nameId = (String)assertionAttributes.get("nameId");
Identity ident;
if(nameId != null) {
// Lookup the identity based on nameId
ident = context.getObject(Identity.class, nameId);
}
return ident;
i need to ensure from one thing is there additional information needed to be added in other login configuration taps while enabling the SSO configuration using SAML Based Single Sign-On (SSO)?
i solved the problem the reason was there are some missing tables in the identityiq database that cause the issue so i run the script of creating the tables again to complete the missing tables then the problem solved in SailPoint GUI