Hello,
I am working with on-prem ISAM 9.0.7 and exploring the OAuth Authorization Code flow. As per ISAM MMFA configurations using the wizard on the ISAM LMI, the transaction endpoint created for use by OAuth clients is:
https://<webseal-ip>/scim/Me?attributes=urn:ietf:params:scim:schemas:extension:isam:1.0:MMFA:Transaction:transactionsPending,urn:ietf:params:scim:schemas:extension:isam:1.0:MMFA:Transaction:attributesPendingThis transaction endpoint is working fine with one of my ISAM lab environments and showing the following results (which are expected):
{ "meta": { "location": "https://192.168.10.186/scim/Users/amFoYW56YWli", "resourceType": "User" }, "schemas": [ "urn:ietf:params:scim:schemas:core:2.0:User", "urn:ietf:params:scim:schemas:extension:isam:1.0:MMFA:Transaction" ], "id": "amFoYW56YWli", "urn:ietf:params:scim:schemas:extension:isam:1.0:MMFA:Transaction": { "attributesPending": [], "transactionsPending": [] }, "userName": "jahanzaib"}However, in another similar ISAM environment (with same configurations) this same endpoint is returning different results as shown below:
{ "meta": { "location": "http://10.180.142.215:81/scim/Users/c3ZjX3VhdF9pYW1fdXNy", "resourceType": "User" }, "schemas": [ "urn:ietf:params:scim:schemas:core:2.0:User" ], "id": "c3ZjX3VhdF9pYW1fdXNy", "userName": "svc_uat_iam_usr"}It can be observed that
urn:ietf:params:scim:schemas:extension:isam:1.0:MMFA:Transaction schema is missing in result from the second environment.
What could be causing this difference?
Best regards,
------------------------------
Jahanzaib Sarwar
------------------------------