Working With Tenants

about the tenants workspace the information on this page is populated by the system configuration wizard although there is a lot of information in this workspace, you should only do the following tasks from within this workspace reset the cache for a tenant see resetting the cache for a tenant docid\ ffzfqgwxwntbmmr5sbozh add a certificate if you want to use saml authentication, you must upload a certificate and password so that end users can download it see adding a certificate to a tenant docid\ ffzfqgwxwntbmmr5sbozh capture audit files from ism discovery, to help with troubleshooting see capturing discovery messages for debugging docid\ ffzfqgwxwntbmmr5sbozh configure how users attach files see configuring attachment options docid\ ffzfqgwxwntbmmr5sbozh set metadata to read only see setting production metadata to read only docid\ ffzfqgwxwntbmmr5sbozh set the login url see setting the login url docid\ ffzfqgwxwntbmmr5sbozh resetting the cache for a tenant caches information about each tenant in the configdb because of this, changes to the tenant, such as updating the status, database information, and so on, are not immediately reflected in the corresponding tenant this can lead to situations where allows a user to log into a tenant, even though the status of the corresponding tenant in the configdb is set to closed to manually reset the cache for a specific tenant, do the following log in to the configdb from the workspace selector bar, select tenants the system displays the tenants workspace highlight the tenant to reset the cache for click reset tenant cache adding a certificate to a tenant if your implementation includes multiple tenants, the certificate should be for the domain and not the specific tenant for example, the certificate for cloud tenants is for saasit com, not for a specific tenant such as mytenant saasit com log in to the configdb from the workspace selector bar, select tenants the system displays the tenants workspace double click the tenant for which to add a certificate click add certificate navigate to the certificate location highlight it and click open enter the password for the certificate in the certificate password field click save capturing discovery messages for debugging perform the following procedure if you are using discovery and you need to capture the audit files sent to the server from the discovery client agents after you capture the audit files, you can review them in a debug environment to find out more details about the problem the logging can be very long, so be careful about using this feature for more information, see the online help log in to the configdb from the workspace selector bar, select tenants the system displays the tenants workspace double click the tenant to configure logging for check log failed im message click save configuring attachment options perform the following procedure to configure how attachments are saved you may need to change the format for storing files if users regularly store very large files, such as system log files after you configure this, when a user saves an attachment to a record, the attachment is stored in the location that you specified here for information about saving attachments as a file stream, see https //msdn microsoft com/en us/library/gg471497 aspx https //msdn microsoft com/en us/library/gg471497 aspx we recommend that for system data, such as icons and images, you select database for the attachment save type field log in to the configdb from the workspace selector bar, select tenants the system displays the tenants workspace double click the tenant for which to configure attachment options for the attachment save type field, select a type database , filestream , file system , amazon s3 , or azure blob for the attachment path field, enter the default path where attachments are saved click save setting production metadata to read only if a user makes a change to the metadata in the production instance of the tenant, such as when configuring a workflow for a request offering, but does not make the same change in the uat or staging instance of the tenant and then pushes the data from the uat or staging instance of the tenant to the production instance of the tenant, the data becomes corrupt and the workflow fails to avoid this, set the metadata on the production instance of the tenant to read only follow these steps log in to the configdb from the workspace selector bar, select tenants the system displays the tenants workspace double click the tenant for which to set the production metadata to read only check is production metadata read only click save if a user tries to edit the workflow for a request offering, the system displays a message stating that the production metadata is read only and cannot be edited see "working with request offerings" in the online help for more information setting the login url set the login url in the following scenarios when configuring active directory authentication using windows integrated security (wis) this feature allows users to access without entering their user name and password this procedure is only valid for the on premises version of when configuring the on premises url for mobile users follow these steps log in to the configdb from the workspace selector bar, select tenants the system displays the tenants workspace double click the tenant for which to set the login url in the login url field, enter the url where users go to log in click save setting the alternate login url (vanity url) for an msp besides setting the login url as described above, you can also specify an alternate login url, also known as a vanity url, for a managed service provider (msp) follow these steps log in to the configdb from the workspace selector bar, select tenants the system displays the tenants workspace double click the tenant for which to set the alternate login url (vanity url) at the bottom, click the alternate login url tab click new tenanturlalias the system displays the new tenanturlalias dialog box in the url field, enter the alternate login url (vanity url) click save