Tthis page describes how to configure Basic HTTP authentication for incoming and/or outgoing authentication for an application link.

Basic HTTP authentication allows Crucible to provide a specific set of user credentials to a remote application and vice versa. Once authenticated, one application can access specified functions on the other application on behalf of that user. For example, if you supply the credentials of a Crucible administrator on your Crucible server to a remote application, the remote application will be able to access all functions on your Crucible server that the Crucible administrator can access.

This method of authentication relies on the connection between Crucible and the remote application being secure. We recommend that you use Trusted Applications authentication or OAuth authentication for your application link instead, if possible.

On this page:

開始する前に

Configuring Basic HTTP Authentication for Outgoing Authentication

Configuring outgoing basic http authentication will allow Crucible to trust a remote application. This allows the remote application to access specified functions in Crucible.

To configure basic http authentication for an outgoing application link:

Configuring Basic HTTP Authentication for Incoming Authentication

Configuring incoming basic http authentication will allow the remote application that you are linking to, to trust Crucible. Crucible will be able to access specified functions on the remote application.

To configure basic http authentication for an incoming application link:

関連トピック

Configuring OAuth Authentication for an Application Link
Configuring Trusted Applications Authentication for an Application Link