Does API allows to assign asset owner to an LDAP user not re
Hi guys,
We have some doubts related with API submission that you may resolve quickly.
The GUI allows to define an owner asset user straight from LDAP without force the user to be defined in RAM. Is that possible to do through API using method setOwners from class RAMAsset? Do you find any problem doing this? We thought that is possible as the GUI allows why the API does not?
We have some doubts related with API submission that you may resolve quickly.
The GUI allows to define an owner asset user straight from LDAP without force the user to be defined in RAM. Is that possible to do through API using method setOwners from class RAMAsset? Do you find any problem doing this? We thought that is possible as the GUI allows why the API does not?
2 answers
When you sets an un registered owner in the Web UI, the server will implicitly registers the user with RAM (using LDAP uid information). This is based on the fact the the UI first allowed you to search for a valid uid in LDAP before that implicit registration.
In the API, it is very possible that the uid is not a valid LDAP uid and is the reason it does not work...
Though I do not see why we can not assume that the API is using a valid uid, perform an implicit registration (with a "force" option), and fail if it is not a valid uid.
In the API, it is very possible that the uid is not a valid LDAP uid and is the reason it does not work...
Though I do not see why we can not assume that the API is using a valid uid, perform an implicit registration (with a "force" option), and fail if it is not a valid uid.