WSO2 Identity Server external LDAP throws OBJECT_CLASS for OID identityperson does not exist

戏子无情 提交于 2019-12-06 06:36:53

This is because WSO2 IS uses set of customized object classes in order to achieve some tasks such as SCIM. Since you are using en external LDAP either you can change the schema of the LDAP or you can map those attributes using claim mappings.

Since you are using ApacheDS, you can use the LDIFs to change the schema of your LDAP. You can find ldif files under /repository/data/org.wso2.carbon.directory/schema/ou=schema

If you do not wish to change the schema, easy way is to change the claims. For example, you have got an error saying 'accountlock' doesn't exists. This means IS trying to insert some value to a attribute within LDAP. Attribute name is 'accountlock'. This is controlled from claim mappings (Home > Configure > Claim Management in IS). There you can find set of claim dialects are displayed.

If you go in to these dialects, you can find set of claims are there. I take the accountlock attribute as an example. Under http://wso2.org/claims dialect, you can find 'Account Locked' attribute is there. You can change the value (Mapped Attribute) of that claim to an existing attribute in youe LDAP. This existing attribute needs to be a string type attribute. This process can be repeated for each missing attribute.

Hope this helps

易学教程内所有资源均来自网络或用户发布的内容,如有违反法律规定的内容欢迎反馈
该文章没有解决你所遇到的问题?点击提问,说说你的问题,让更多的人一起探讨吧!