One of our developers has the following question in terms of how Appian works.
In our use case,
1. The user information is stored in 3 places:
1.1. application defined CDTs/tables,
1.2. Appian internal user management system,
1.3. Active Directory (AD, whose communication is mainly managed via .NET services)
2. Logically, the user information in those 3 places are for the same user community. ex. username "jsmith" in all 3 places should be for the same person "John Smith" per business logic. i.e. the user data should be in sync in all 3 places.
3. When adding/updating/removing a personnel/user from our Appian application screen, the Appian process can create/update/remove the same user data stored in 1.1. and 1.2.
4. After 3., Appian process needs to call a .net provided web service to Add/Update/Remove the same user data stored in 1.3.
5. SSO/SAML between .NET and Appian is already set up in our Appian instance, but currently there may be some issues with that.
Question: is the user data stored, as separate copies, in both 1.2. and 1.3.? Or, is the user data only stored in 1.3. (AD)? Or only in Appian (1.2.)....?
Discussion posts and replies are publicly visible