We want to onboard an application that supports both SCIM 2.0 and has a REST API. We initially onboarded it as a SCIM connector, however, one of the needed attributes for our use case which is the lastLoginDate is not available in their SCIM schema. It is only available on their REST API but their REST API does not support user management endpoints like user account creation and deactivation.
With this is, is it possible to use the SCIM for user management use cases (ex. access request for account creation, account termination and account deletion) and use the REST API just for extracting the lastLoginDate? And what would be the impact of this and would it still be scalable in the long run?
Hi @jasmedina
Would you mind sharing the name of the application? although you could create an additional source for this purpose the question of is it scalable/usable will depend on how you intend the use the last login date, this may restrict your options.
I will be using it to delete an account in the application after x number of days. Would that work using a rule in SCIM or should I attach the rule in the webservice connector?
The application name is Miro. I will be using the lastLoginDate to disable an account after x number of days and delete the account in Miro after x number of days.
Hi @jasmedina
Just had a look at the api documentation, they have a common api base url you may be able to have a single web services connector covering both requirements, however that will require you to redevelop the SCIM functionality you require into a new web services connector targeting the Miro setup.
This was what I thought also but their support just confirmed that it was not supported by their REST APIs so it was a little confusing. Would you be able to share the link to the documentation you found? Thank you!!
