Challenge Overview
- Solution must authenticate to multiple domains via OAuth 2 to extract profile information that will be stored within the solution.
- Authentication methods to the app domains for the profile information through the directory API can be through web client or service client but should not require a web login.
- Credentials can be stored in a config file or or managed via an admin area that you create. ����
- The extraction of profile information should occur within a backend process in case this process takes more than the 60 second deadline.
- The extraction process will eventually be run on a regular basis so if it is re-run it must not create duplicates. ����
- The solution should exclude profiles if they are in a given organizational unit (OU). ����A list of OU��������s can be stored within a config file or managed via an admin area that you create. ����There will be no OU management from this app but that information should be pulled from the profiles.
- The solution should exclude profiles if they are in a given group. A list of groups to exclude can be stored within a config file or managed via an admin area that you create.
- The solution should not collect personal or shared contacts.
- The fields that should be captured are ones that are loaded into the profile via GADS you can find a list of these fields in Google��������s documentation. ����Not all fields need to be displayed but should be stored.
We currently have one Apps Domain account that a challenger can authenticate against. ����Please contact us if you want to use this apps domain. ����
If you want to have a free trial domain you can get one here 30 Day free trial.
����