Update README.md to reference Integrator accounts. (#130)

* Update README.md to reference Integrator accounts.

* Edit steps for correctness.

* Edit origin port for correctness.

* Update steps for cloning the repo and modifying the config file.

---------

Co-authored-by: jcavazos <jcavazos@itpops.com>

Author: cavazosjoe

README.md

@@ -9,23 +9,44 @@ It also shows how to return the user's information from an API using an OAuth 2.
 Before running this sample, you will need the following:
 
 * [Java 17+](https://sdkman.io/jdks)
-* [The Okta CLI Tool](https://github.com/okta/okta-cli/#installation)
-* An Okta Developer Account, create one using `okta register`, or configure an existing one with `okta login`
+* An Okta Integrator Free Plan account. To get one, sign up for an [Integrator account](https://developer.okta.com/login). Once you have an account, sign in to your [Integrator account](https://developer.okta.com/login). Next, in the Admin Console:
+
+1. Go to **Applications > Applications**
+2. Click **Create App Integration**
+3. Select **OIDC - OpenID Connect** as the sign-in method
+4. Select **Web Application** as the application type, then click **Next**
+5. Enter an app integration name
+6. Configure the redirect URIs:
+  - Accept the default redirect URI values:
+  - **Sign-in redirect URIs:** `http://localhost:8080/login/oauth2/code/okta`
+  - **Sign-out redirect URIs:** `http://localhost:8080`
+7. In the **Controlled access** section, select the appropriate access level
+8. Click **Save**
+
+Creating an OIDC Web App manually in the Admin Console configures your Okta Org with the application settings. You may also need to configure trusted origins for `http://localhost:8080` in **Security > API > Trusted Origins**.
 
 ## Get the Code
 
-Grab and configure this project using `okta start spring-boot`.
-
-> **NOTE**: If you'd like to use WebFlux instead of Spring MVC, use `okta start spring-boot --branch webflux`.
-
-You can also clone this repo and run `okta start` in it.
-
 ```bash
 git clone https://github.com/okta-samples/okta-spring-boot-sample.git
 cd okta-spring-boot-sample
-okta start
 ```
 
+Update your config file at `.okta.env` with the values from your application's configuration:
+
+```text
+ISSUER=https://dev-133337.okta.com
+CLIENT_ID=0oab8eb55Kb9jdMIr5d6
+CLIENT_SECRET=NEVER-SHOW-SECRETS
+```
+
+### Where are my new app's credentials?
+
+After creating the app, you can find the configuration details on the app’s **General** tab:
+- **Client ID:** Found in the **Client Credentials** section
+- **Client Secret:** Click **Show** in the **Client Credentials** section to reveal
+- **Issuer:** Found in the **Issuer URI** field for the authorization server that appears by selecting **Security > API** from the navigation pane.
+
 ## Enable Refresh Token
 
 Manually enable Refresh Token on your Okta application to avoid third-party cookies. Sign in to your Okta Developer Edition account. Press the **Admin Console** button to navigate to the Okta Admin Console. In the sidenav, navigate to **Applications** > **Applications** and find the Okta application for this project named `okta-spring-boot-sample`. Edit the application's **General Setting** to enable the **Refresh Token** checkbox. **Save** your changes.