Skip to main content Skip to footer

Creating a 3-legged OAuth Application in IDCS

Where is the simple "shake 'n' bake" / step by step guide to creating a 3-legged, Authorization Code flow OAuth client in IDCS?

Right here!

1: From the Dashboard in IDCS click the + under Applications to create a new Application

2: Select Confidential Application because we're creating a 3-legged app

3: Fill in the first screen

Only name is required, and if you aren't sure what the other fields mean that's all you should enter.

4: Configure the App

IDCS supports basically all of the OAuth 2 grant types so we need to tell it what kind of app we're using

On this screen you need to:

a. select "Configure this application as a client now" to light up the rest of this screen.

b. select Authorization Code (since that's the kind of app we want)

c. Provide the Redirect URL. After the user logs in and IDCS creates an Authorization Code it will send the user's browser to this URL with that code as a query string parameter. If you don't know what should go here check your application's documentation.

5: Next your way through the "Resources", "Web Tier Policy", and "Authorization" screens

We don't need any of that for this application so just hit Next until you get to the last screen and can click the Finish button

6: Click finish and you will be shown the Client ID and Secret

NOTE: Don't go away, there's still one more step!

You are going to need these to configure your app so copy/paste these values somewhere safe.

7: Click Activate

By default IDCS creates new apps in a disabled / unactivated state. Until you click the Activate button your client app will not be able to talk to IDCS.

Click the Activate button in the upper right hand corner, and then click the green Activate button

8: Note the green status bar telling you that you're all set

Congratulations! You've created your first OAuth client in IDCS.

Your app can now force users to log in via IDCS and you can figure out who the user is. Apps that use IDCS as their OAuth server can do quite a bit more, but that's a subject for another post.

About the author

Keith M. Curran

Keith Curran is the former CEO of BESI LLC, a global education provider.  He is the former director of development for the WSU Farmers Network and presently Director of Information Technology for the DIFM - CIG Oracle Cloud Tenancy at the University of Connecticut. 

UConn Agriculture

March 07, 2023

Integration with Oracle IDCS Complete!

The DIFM Ag Research Portal and Farmers Portal is now integrated with Oracle IDCS and there is self-registration for farmers and research scientists.   Both applications remain under development but the underlying scaffolding is built and being tested.

Ag Research Portal:  Is an end-user application under development designed for PI's and Stakeholders to access, review, edit migrated data residing in DIFM's Autonomous Data Warehouse in the Oracle Cloud.  

Farm Portal: Is an end-user application allowing farmers to register for OFPE Trials, upload necessary data for implementing those trials.  

Integrating user registration with IDCS and managing application & data access with IDCS satisfies essential requirements of Phase I of the software development plan.