ldap - Wso2 Scim extentinon datatype error -


so extending scim api wso2. when create extension using datatype string extensions work correctly. in ldap have lot of other custom attributes , attributes use other datatype string operational or telephone number.

i tried change datatype value 1 of extended attributes when requesting attribute through scim api, leads me 500 error.

this example of scim extension configuration

[{ "attributeuri":"urn:scim:schemas:extension:enterprise:1.0:enterprise.homephone", "attributename":"homephone", "datatype":"telephone number", "multivalued":"false", "multivaluedattributechildname":"null", "description":"the user's phone", "schemauri":"urn:scim:schemas:extension:enterprise:1.0", "readonly":"false", "required":"false", "caseexact":"false", "subattributes":"null" },  { "attributeuri":"urn:scim:schemas:extension:enterprise:1.0:enterprise.sharedirectory", "attributename":"sharedirectory", "datatype":"string", "multivalued":"false", "multivaluedattributechildname":"null", "description":"the user's share dir", "schemauri":"urn:scim:schemas:extension:enterprise:1.0", "readonly":"false", "required":"false", "caseexact":"false", "subattributes":"null" },  { "attributeuri":"urn:scim:schemas:extension:enterprise:1.0", "attributename":"enterprise", "datatype":"null", "multivalued":"false", "multivaluedattributechildname":"null", "description":"scim wso2 user schema extension", "schemauri":"urn:scim:schemas:extension:enterprise:1.0", "readonly":"false", "required":"false", "caseexact":"false", "subattributes":"homephone sharedirectory" }] 

how can use these attributes in scim api? need special configuration?

there set of data types supported scim. have map data types in userstore these.

+-----------+-------------+-----------------------------------------+ | scim data | scim schema | json type                               | | type      | "type"      |                                         | +-----------+-------------+-----------------------------------------+ | string    | "string"    | string per section 7 of [rfc7159]       | |           |             |                                         | | boolean   | "boolean"   | value per section 3 of [rfc7159]        | |           |             |                                         | | decimal   | "decimal"   | number per section 6 of [rfc7159]       | |           |             |                                         | | integer   | "integer"   | number per section 6 of [rfc7159]       | |           |             |                                         | | datetime  | "datetime"  | string per section 7 of [rfc7159]       | |           |             |                                         | | binary    | "binary"    | binary value base64 encoded per section | |           |             | 4 of [rfc4648], or url ,         | |           |             | filename safe alphabet url per section  | |           |             | 5 of [rfc4648] passed json | |           |             | string per section 7 of [rfc7159]       | |           |             |                                         | | reference | "reference" | string per section 7 of [rfc7159]       | |           |             |                                         | | complex   | "complex"   | object per section 4 of [rfc7159]       | +-----------+-------------+-----------------------------------------+ 

reference: https://tools.ietf.org/html/rfc7643#section-2.3


Comments

Popular posts from this blog

Is there a better way to structure post methods in Class Based Views -

performance - Why is XCHG reg, reg a 3 micro-op instruction on modern Intel architectures? -

jquery - Responsive Navbar with Sub Navbar -