You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Currently CR allows to sync users with LDAP server only. I think we can add new custom script type with 1 method:
List loadSourceServerEntries(return_attributs, conf, etc)
In this method customer can implement logic to get data from RDBMS, MySQL, etc..
CR doesn't require major changes. For CR perspective instead of loading data from LDAP custom script method will return data need to finish iteration.
After that customers can add simple authentication script which will do authentication against RDBMS instead of AD LDAP.
The text was updated successfully, but these errors were encountered:
@yurem, do we really need a separate web UI's tab for that? Mb it's possible to add another function user can redefine to the current CR's class(es), which, if implemented by user, will took over/override the part of CR's functionality responsible for getting data from LDAP, while not touching the other its parts? It just would appear more intuitive, imo, so easier to document and explain to users :) If it doesn't over-complicate things from app architecture's point of view, of course.
Currently CR allows to sync users with LDAP server only. I think we can add new custom script type with 1 method:
List loadSourceServerEntries(return_attributs, conf, etc)
In this method customer can implement logic to get data from RDBMS, MySQL, etc..
CR doesn't require major changes. For CR perspective instead of loading data from LDAP custom script method will return data need to finish iteration.
After that customers can add simple authentication script which will do authentication against RDBMS instead of AD LDAP.
The text was updated successfully, but these errors were encountered: