S

Sebastien

Back to Challenges
Connect

Create a Provider + Connection

Not started
12 points
Intermediate
~30 min
Connect
Auto-verified from Console activity

Intermediate challenge: create and authorize a provider connection for an agent that needs access to a protected system. You need this when the agent or one of its Tools must act with a user's identity or a configured service identity; complete the consent or secret exchange, then retry the request with the connected identity.

Why this challenge?

Connections let each user authorize access explicitly and within scope. That keeps protected systems protected while still allowing an agent to act on the user's behalf.

How do you want to work?

Choose your preferred workflow. All paths reach the same outcome — pick what fits your style.

This intermediate path teaches the three-part model: the Provider is the reusable authentication recipe, the Connection is the principal-specific credential, and the Requirement tells the agent or Tool which Connection to resolve at runtime.

Console journey

Move through this journey one milestone at a time. Each step opens the place you need next.

  1. 1
    Open the agent and identify the requirement

    Open the agent that will use the protected Tool and identify which operation needs authentication. Start with a safe request so you can see the requirement in context.

    Open in Console
  2. 2
    Understand the Provider

    A Provider is a reusable authentication recipe. In the Tool wizard, open the Security step to select an existing Provider or choose Add a new provider for this tool. Self-service creation supports three-legged OAuth for a user; two-legged OAuth and API-key Providers require the platform team.

    Open Tool wizard Read Help
  3. 3
    Create the Connection

    Create the principal-specific credential Connection from the selected Provider. Choose the user or service identity, complete consent or provide the approved secret reference, and wait for the Connection to become available.

    Read Help
  4. 4
    Authorize and attach the Connection

    There is no permanent Connect tab. The agent or Tool declares a Requirement for the Provider, and a protected request triggers the connection prompt or Connect button. Complete the authorization so the Requirement can resolve the Connection server-side.

    Read Help
  5. 5
    Retry and confirm

    Send the safe request again and confirm the protected operation succeeds with the connected identity while the credential value remains hidden.

    Choose an agent Read Help
Ask the Deere AI Assistant

Stuck? The Deere AI Assistant in the Console doesn't know about this quest by default. Download the AI Quest Challenges guide below and upload it into the Assistant so it has context, then ask for help connecting or building this.

Download the AI Quest Challenges guide
Choose an agent View Documentation

This challenge is verified automatically from your real Console activity.