Connect Reference
- 4 Sub categories
- 5 Articles
- 4 Sub categories
- 23 Articles
Community Adapter Actions
- 2 Articles
- 1 Articles
- Published on Aug 19, 2022
These are some examples of Action Sets that can be used in RapidIdentity Connect for various purposes. To use these, download the code example provided. Then, make any changes that apply to your environment and purpose, save as .xml, then Import tha...
- Published on Mar 30, 2022
RapidIdentity Connect - Best Practices These are the best practices known and used by the Identity Automation Services team and are based on internal deployment standards. Naming Conventions
- Published on Mar 30, 2022
General Standards Proper Use of Core and Custom Schema Definitions Do not store values in a core schema that doesn’t describe the data. For example, don’t store a job code value in the physicalDeliveryOfficeName attribute. Storing Em...
- Published on Mar 30, 2022
Table of Contents RapidIdentity Connect Security Considerations RapidIdentity Connect projects are containers for a set of related resources such as Action Sets, files, job definitions, RESTPoint definitions, OAuth2 credentials, and OAuth1 consu...
- Updated on Jul 19, 2022
- Published on Jul 19, 2022
Occasionally while troubleshooting an issue, Identity Automation Support may request that you send them the Action Set that you're working in so that they can investigate it more closely. This is simple to do and a powerful way for Support to really...
- Published on Nov 7, 2022
Purpose
The openADChangeIterator action in RapidIdentity Connect relies on a change cookie to limit the number of processing between systems to only records that have changed since the previous sync. On occassion, these change cookies can become...