contentACCESS documentation version 3.1 with service pack

  1. Introduction to contentACCESS
    1. Services provided by contentACCESS
    2. Software requirements
  2. contentACCESS setup package
    1. Installation of contentACCESS
  3. contentACCESS components
    1. contentACCESS Central Administration
      1. Central administration login
      2. Automated single sign on
      3. Central Administration logout
      4. contentACCESS Central Administration user interface
    2. contentWEB
      1. Logging in to contentWEB
      2. Automated single sign on
    3. Virtual drive
    4. contentACCESS Web Services (Proxy)
    5. Central login page
  4. contentACCESS Tools
    1. Installing Outlook forms
    2. Legacy email archive connectors
    3. Legacy archive connector for Metalogix Archive Manager Exchange Edition (MAM EE)
    4. Legacy archive connector for Email Lifecycle Manager (ELM)
    5. Installing TECH-ARROW’s WinShortcutter
  5. Tenants in contentACCESS
    1. How to create a new tenant
    2. Tenant limitations
    3. How to provide access to a tenant (adding new tenant administrators)
    4. Tenant administrator invitation types
  6. General system configurations
    1. Connection
    2. User interface
    3. Users in contentACCESS
    4. Invitations
    5. Roles
      1. Creating roles
      2. Role details
      3. Role assignment
      4. Defining specific permissions of a role assignment
      5. Editing roles, editing role assignments
      6. General use cases of how to create/assign roles
      7. Managing access to contentACCESS objects
    6. Login providers
      1. Login providers’ context menu options
      2. External login provider configuration
      3. Associating an enabled provider with a user login
      4. contentACCESS users in third party systems
    7. System
    8. Licensing
      1. How to activate your license key
    9. Notifications
    10. Monitoring — how to find out possible misconfigurations / reasons of potential system/job failures
    11. Distributed environment in contentACCESS — Clusters
    12. Statistics
    13. How to create/configure databases — All databases
  7. Common features
    1. Databases
    2. Schedules
    3. Retentions
    4. Storages
    5. Exchange connections
      1. Exchange performance settings – turning off the Exchange throttling policies
      2. Hybrid Exchange environments in the Email Archive system
    6. Importing contentACCESS configurations from files
      1. Manual import of Exchange servers/groups/mailboxes to the contentACCESS Address book
      2. Importing File Archive root folders to be archived
  8. Creating new jobs in contentACCESS
  9. Jobs’ page, jobs’ context menu
  10. File Archive
    1. Introduction to File system archive
    2. File Archive settings
    3. Databases
    4. System settings
    5. Retentions
    6. Storages
    7. Root folders
    8. Aliases
    9. Schedules
    10. Provisioning settings and managing access to contentWEB
    11. Configuring aliases
    12. Configuration of jobs available in contentACCESS File Archive
    13. Configuration of File system archive job
    14. Configuration of a File system restore job
    15. Configuration of File system recovery job
    16. Configuration of Remote shortcutting job
    17. Active/inactive documents in File system archive
  11. Email Archive
    1. Important settings before creating an Email Archive job
    2. Database settings
    3. System settings
    4. Provisioning settings
    5. Retention settings
    6. Shortcuts in email archiving
    7. Storing of archived emails
    8. Creating email archive schedulers
    9. User experience
    10. Exchange 2013+: Mail app in OWA 2013+ or on MS Outlook 2013+ desktop version
    11. Exchange 2010: OWA 2010 integration
    12. Address book objects
    13. Granting access rights for mailbox users and explicit users to view the mailbox archive
    14. Creating contentWEB users (option 1)
    15. Manage access to a mailbox archive (option 2)
    16. Database and store assignment in email archiving
    17. How to assign database and storage to an Exchange group?
    18. How to assign database and storage to a mailbox?
    19. How to move data from source database/storage into a second (target) database/storage?
    20. Creating Email archive jobs: archive, restore, recovery, mailbox move, shortcut synchronizaion, shortcut repair
    21. Email archive job
      1. Email archive job configuration
    22. Email restore job
      1. Email restore job configuration
    23. Email recovery job
      1. Email recovery job configuration
    24. Mailbox move job
      1. Mailbox move job configration
    25. Shortcut synchronization job
      1. Shortcut synchronization job configuration
    26. Shortcut repair job
      1. Shortcut repair job configuration
    27. Public folder archiving
      1. How to configure a job to archive public folders
      2. Public folders in the contentWEB archive
      3. User permissions to public folders
      4. Public Folder archiving in hybrid Exchange environments
  12. SharePoint archive plugin
    1. SharePoint Archive settings
    2. SharePoint Archive job configuration
    3. SharePoint recovery job configuration
    4. SharePoint Publishing job
    5. SharePoint in the contentWEB archive
  13. Custom plugins
    1. Email management job configuration
    2. Storage replication plugin
    3. Sharing plugin
    4. Datengut plugin
    5. Email synchronizer plugin
  14. officeGATE
  15. accessGATE Mobile
  16. Virtual drive configurations
  17. Application settings
  18. Terms of use
  19. FAQ

6.6.2.External login provider configuration

To configure a new login provider, click +new on the Logins provider page. The Login providers dialog will open which requires to:

  • name the provider,
  • choose a supported external provider from the Provider type list,
  • set the provider availability – here you may set the applications that will use the given provider
  • fill the required fields – detailed below for the provider types
  • and click on OK to save the settings.


Configuring Google OAuth:

contentACCESS supports Google authentication as well. Would you like to use it, you need to apply for a Client ID and Client Secret by registering the contentACCESS application on the Google Developers Console page first. Open the page, sign in with your Google account and follow these steps:

  1. Click “Create a project” in the upper right “Select a project” menu:
  2. login prov3

  3. Name your project and create it:
  4. login prov4

  5. If the API Manager page isn’t already open, open the console menu and select “API manager”. On the left, click “Credentials”.
  6. login prov5

  7. Click “Create credentials”, then select “OAuth client ID”.
  8. login prov6

  9. If this is your first time creating a client ID, configure your consent screen by clicking “Configure consent screen”.
  10. login prov7

  11. Enter the product name and fill the optional fields if you want. Save your settings.
  12. login prov8

  13. Select the WEB application type for your project and enter JavaScript Origins, redirect URLs or both to the appropriate text fields.
  14. login prov9

    Use the URLs accessible in the Google login provider’s window in contentACCESS Central Administration, like in the blue frame on the picture below.

    login prov10

  15. Click “Create” on the Google developers console and the Client ID and Client Secret will be created automatically. Save these values somewhere on your computer:

login prov11

Now configure your Login provider in contentACCESS Central Administration. Open the Login providers page (System => Security => Login providers), click here on “+new”. In the Login providers window name your provider, select Google provider type and choose the application that should use this authentication type. Further enter the Client ID and Client Secret from step 8) to the respective text fields, and click OK.

login prov12

Configuring Azure login provider:

contentACCESS supports log in using your Microsoft account. The first thing you need to do is to register an application (contentACCESS) under your Microsoft account. We used personal account for the registration in our use case below.

  1. Go to the Windows Live application management site and sign in.
  2. Click “Add an app“ and name your application. The name that you specify should contain only alphanumeric characters and cannot be changed after registration is complete.
  3. login prov13

    login prov14

  4. The Application ID will be later used as the Client ID in your application (in the Login provider’s window of contentACCESS Central Administration).
  5. login prov15

  6. Click option Generate New Password. This will be the ClientSecret in your application. You should record this key, but we recommend that you do not store it in the same location as its corresponding client ID:
  7. login prov16

  8. Choose your application platform: Click “Add platform” and choose “Web“.
  9. login prov17

  10. Now you can specify the redirect URIs (– more with clicking on the Add Url button). Use the URL displayed in the Login provider’s window of the contentCCESS Central Administration.

    Sample: https://[contentACCESS_Server:Port_Number]/CentralAdministration/LoginOAuth2.aspx/oauth2callback

  11. Important: Microsoft OAuth requires to use secure protocol – HTTPS – for the contentACCESS Central Administration URL.

    login prov18

  12. Upload your application logo, add terms of services and Privacy Statement. If you want to use the personal accounts too, you need to check the Live SDK support. Save your changes.
  13. login prov19

    Now configure the Azure login provider in the contentACCESS Central Administration.

  14. Open the Login providers page (System => Security => Login providers) and click +new. Name your provider, select the “Azure” provider type and specify the applications that will use the Azure login (All applications/contentACCESS only/contentWEB only/Client applications only). Enter the Client ID and ClientSecret from steps 3) and 4) above and click “OK”.
  15. login prov20

    With this step, this new login provider configuration has been enabled in contentACCESS. A user can use the configured login provider if this login type is associated with him. In the following subchapter we will learn how to associate a login type with a user.

Yes No Suggest edit
Help Guide Powered by Documentor
Suggest Edit