Skip to content
This repository was archived by the owner on Feb 11, 2023. It is now read-only.

Commit 2fdc50b

Browse files
committed
Incorporated consistency feedback from payton, added a section for new option to README.md
1 parent 2d8b3c7 commit 2fdc50b

File tree

3 files changed

+21
-2
lines changed

3 files changed

+21
-2
lines changed

README.md

100644100755
+19
Original file line numberDiff line numberDiff line change
@@ -100,6 +100,25 @@ Session duration is defined as the number of hours that the JWT is valid for. Af
100100
1. Choose `CENTRIFY` as the authorization method and enter the values for Base URL (Centrify Resource application URL), Client ID, Client Secret, Redirect URI, and Session Duration (which is available from the **Tokens** tab).
101101
1. Upload the resulting `zip` file found in your distribution folder using the AWS Lambda console and jump to the [configuration step](#configure-lambda-and-cloudfront)
102102

103+
### OKTA Native
104+
105+
1. Clone or download this repo
106+
1. Sign in to OKTA with your administrator account and navigate to the `Applications` tab.
107+
1. Add Application
108+
1. Select the `Native` application type
109+
1. Base URI: CloudFront distribution domain name (`https://{cf-endpoint}.cloudfront.net`)
110+
1. Login Redirect URI: CloudFront distribution domain name with callback path (`https://{cf-endpoint}.cloudfront.net/_callback`)
111+
1. Group Assignments: Optional
112+
1. Grant Type Allowed: Authorization Code
113+
1. Done
114+
1. Gather the following information for Lambda configuration
115+
1. Client Id from the application created in our previous step (can be found at the bottom of the general tab)
116+
1. Base Url
117+
1. This is named the 'Org URL' and can be found in the top right of the Dashboard tab.
118+
1. Execute `./build.sh` in the downloaded directory. NPM will run to download dependencies and a RSA key will be generated.
119+
1. Choose `OKTA Native` as the authorization method and enter the values for Base URL (Org URL), Client ID, PKCE Code Verifier Length, Redirect URI, and Session Duration
120+
1. Upload the resulting `zip` file found in your distribution folder using the AWS Lambda console and jump to the [configuration step](#configure-lambda-and-cloudfront)
121+
103122
## Configure Lambda and CloudFront
104123

105124
[Manual Deployment](https://github.com/Widen/cloudfront-auth/wiki/Manual-Deployment) __*or*__ [AWS SAM Deployment](https://github.com/Widen/cloudfront-auth/wiki/AWS-SAM-Deployment)

build/build.js

+2-2
Original file line numberDiff line numberDiff line change
@@ -374,9 +374,9 @@ function oktaConfiguration() {
374374
shell.cp('./authn/openid.index.js', './distributions/' + config.DISTRIBUTION + '/index.js');
375375
} else {
376376
config.PKCE_CODE_VERIFIER_LENGTH = result.PKCE_CODE_VERIFIER_LENGTH || "96";
377-
shell.cp('./code_challenge.js', './distributions/' + config.DISTRIBUTION + '/code_challenge.js');
377+
shell.cp('./code-challenge.js', './distributions/' + config.DISTRIBUTION + '/code-challenge.js');
378378
shell.cp('./authn/pkce.index.js', './distributions/' + config.DISTRIBUTION + '/index.js');
379-
files.push('code_challenge.js');
379+
files.push('code-challenge.js');
380380
}
381381
config.AUTHZ = "OKTA";
382382

File renamed without changes.

0 commit comments

Comments
 (0)