samples-js-angular-1's Introduction

Angular 1 Samples (Deprecated)

Note: This repository is Deprecated.

Okta is not offering updates to this AngularJS (Angular 1) sample.

Our supported modern Angular SDK: https://github.com/okta/okta-oidc-js/tree/master/packages/okta-angular
Samples using our Angular SDK: https://github.com/okta/samples-js-angular
For those continuing to use AngularJs (Angular 1), you can use our okta-auth-js library to build your components:
- https://github.com/okta/okta-auth-js

Introduction

This repository contains the Angular 1 front-end code that can be used along with back-end server samples.

Note: This Angular sample application is only compatible with our Express Sample Application. If you are using a different sample for the back-end or resource server, please check out the 1.10.0 version of this repository.

Please continue to visit https://developer.okta.com to learn about new documentation and sample applications.

Using the built-in Express server

To run this sample:

Clone this repository and navigate to the new directory.

git clone [email protected]:okta/samples-js-angular-1.git
cd samples-js-angular-1

Install the required dependencies.
```
npm install
```
Run the mock Okta server. If you're interested in testing this sample against your own Okta org, follow the steps in the Express Quick Start.
```
npm run mock-okta
```
In a different terminal window, run the Express server.
```
npm start
```
You're all set! Open a browser window to http://localhost:8080.

Note: Use chrome browser if you're running the mock-okta server, to test the sample.

Using your own Okta org

You can create your own Okta org by signing up for a free Developer Account

If you'd like to test this sample against your own Okta org, navigate to the Okta Developer Dashboard and follow these steps:

Create a new Web application by clicking Add Application and selecting Web from the Applications page.
After accepting the default configuration, click Done to redirect back to the General Settings of your application.
Copy the Client ID and Client Secret, as it will be needed for the client configuration.
Finally, navigate to https://{yourOktaDomain}.com/api/v1/authorizationServers/default to see if the Default Authorization Server is setup. If not, let us know. Then, replace the oidc settings in .samples.config.json to point to your new app:

// .samples.config.json
{
  "oidc": {
    "oktaUrl": "https://{{yourOktaDomain}}.com",
    "issuer": "https://{{yourOktaDomain}}.com/oauth2/default",
    "clientId": "{{yourClientId}}",
    "clientSecret": "{{yourClientSecret}}",
    "redirectUri": "http://localhost:8080/authorization-code/callback"
  }
}

Stop the mock-okta server and Express server if you're running it.

Open a new terminal window, and run the Express server.

npm start

You're all set! Open a browser window to http://localhost:8080.

Support

Have a question or see a bug? Email [email protected]. For feature requests, feel free to open an issue on this repo. If you find a security vulnerability, please follow our Vulnerability Reporting Process.

License

Licensed under the Apache License, Version 2.0 (the "License"); you may not use this file except in compliance with the License. You may obtain a copy of the License at http://www.apache.org/licenses/LICENSE-2.0.

Unless required by applicable law or agreed to in writing, software distributed under the License is distributed on an "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied. See the License for the specific language governing permissions and limitations under the License.

samples-js-angular-1's People

Contributors

Stargazers

Watchers

samples-js-angular-1's Issues

Frontend build script fails on Windows

From okta/samples-nodejs-express-4#18

I tried this with

node --version
v7.9.0

on Windows 10. The result:

C:\Users\Nate\Documents\code\samples-js-angular-1 [master ≡]> node .\scripts\build-frontend.js
'DIST_OUT' is not recognized as an internal or external command,
operable program or batch file.
child_process.js:524
    throw err;
    ^

Error: Command failed: DIST_OUT=C:\Users\Nate\Documents\code\samples-js-angular-1\dist npm run build
    at checkExecSyncError (child_process.js:481:13)
    at execSync (child_process.js:521:13)
    at Object.<anonymous> (C:\Users\Nate\Documents\code\samples-js-angular-1\scripts\build-frontend.js:23:1)
    at Module._compile (module.js:571:32)
    at Object.Module._extensions..js (module.js:580:10)
    at Module.load (module.js:488:32)
    at tryModuleLoad (module.js:447:12)
    at Function.Module._load (module.js:439:3)
    at Module.runMain (module.js:605:10)
    at run (bootstrap_node.js:423:7)

Consistent placeholders and labels

Sweep through readme and code to make sure labels and placeholders follow the pattern here: https://oktawiki.atlassian.net/wiki/spaces/UX/pages/470681125/Developer+Experience+-+Okta+Domain+Labels

https://{yourOktaDomain} (not https://{yourOktaDomain}.com)
{clientId}
{clientSecret}

Sample does not work for default auth. server without API AM enabled

For orgs that do not have API Access Management enabled, this sample will not work. I was able to get it to run with an org without API AM enabled by modifying tools/dev-server/route-handlers.js in the following ways:

// url: `${config.oidc.issuer}/v1/token?${query}`,
url: `${config.oidc.issuer}/oauth2/v1/token?${query}`,

and later...

// url: `${config.oidc.issuer}/v1/keys`,
url: `${config.oidc.issuer}/oauth2/v1/keys`,

and also update the value for the Issuer to be https://example.oktapreview.com instead of https://example.oktapreview.com/oauth2/default.

Would you add a warning in the README to notify folks that this sample requires an org with API Access Management enabled?

Broken link to 1.10

The readme says,

If you are using a different sample for the back-end or resource server, please check out the 1.10.0 version of this repository.

The link to 1.10.0 points to a branch that no longer exists. Is this info still relevant?

Recommend Projects

okta / samples-js-angular-1 Goto Github PK