LIGHT

  • News
  • Docs
  • Community
  • Reddit
  • GitHub
Star

OAuth2 Console

In the previous step, we have started the light-router instance for the local portal. It listens 443 for the host lightapi.net

In this step, we are going to explore the lightapi.net UI implementation with a focus on the light-oauth2 view.

For development, we are going to use a proxy to access APIs through light-router. The light-portal view can be accessed from light-portal/view folder.

https://github.com/networknt/light-portal/tree/master/view

proxy

In the src folder, there is a setupProxy.js which contains all the paths for APIs and the target host mapping.

const proxy = require('http-proxy-middleware');

module.exports = function(app) {
  app.use(proxy('/portal/command', { target: 'https://lightapi.net', secure: false }));
  app.use(proxy('/portal/query', { target: 'https://lightapi.net', secure: false }));
  app.use(proxy('/oauth2/client', { target: 'https://lightapi.net', secure: false }));
  app.use(proxy('/oauth2/code', { target: 'https://lightapi.net', secure: false }));
  app.use(proxy('/oauth2/key', { target: 'https://lightapi.net', secure: false }));
  app.use(proxy('/oauth2/refresh_token', { target: 'https://lightapi.net', secure: false }));
  app.use(proxy('/oauth2/service', { target: 'https://lightapi.net', secure: false }));
  app.use(proxy('/oauth2/token', { target: 'https://lightapi.net', secure: false }));
  app.use(proxy('/oauth2/user', { target: 'https://lightapi.net', secure: false }));
};

Start

If you haven’t run the yarn install in the view folder, please do so first.

To start the testing Nodejs server.

yarn start

A browser tab will be automatically started and any code change in the React SPA will be hot loaded by the browser.

  • About Light
    • Overview
    • Testimonials
    • What is Light
    • Features
    • Principles
    • Benefits
    • Roadmap
    • Community
    • Articles
    • Videos
    • License
    • Why Light Platform
  • Getting Started
    • Get Started Overview
    • Environment
    • Light Codegen Tool
    • Light Rest 4j
    • Light Tram 4j
    • Light Graphql 4j
    • Light Hybrid 4j
    • Light Eventuate 4j
    • Light Oauth2
    • Light Portal Service
    • Light Proxy Server
    • Light Router Server
    • Light Config Server
    • Light Saga 4j
    • Light Session 4j
    • Webserver
    • Websocket
    • Spring Boot Servlet
  • Architecture
    • Architecture Overview
    • API Category
    • API Gateway
    • Architecture Patterns
    • CQRS
    • Eco System
    • Event Sourcing
    • Fail Fast vs Fail Slow
    • Integration Patterns
    • JavaEE declining
    • Key Distribution
    • Microservices Architecture
    • Microservices Monitoring
    • Microservices Security
    • Microservices Traceability
    • Modular Monolith
    • Platform Ecosystem
    • Plugin Architecture
    • Scalability and Performance
    • Serverless
    • Service Collaboration
    • Service Mesh
    • SOA
    • Spring is bloated
    • Stages of API Adoption
    • Transaction Management
    • Microservices Cross-cutting Concerns Options
    • Service Mesh Plus
    • Service Discovery
  • Design
    • Design Overview
    • Design First vs Code First
    • Desgin Pattern
    • Service Evolution
    • Consumer Contract and Consumer Driven Contract
    • Handling Partial Failure
    • Idempotency
    • Server Life Cycle
    • Environment Segregation
    • Database
    • Decomposition Patterns
    • Http2
    • Test Driven
    • Multi-Tenancy
    • Why check token expiration
    • WebServices to Microservices
  • Cross-Cutting Concerns
    • Concerns Overview
  • API Styles
    • Light-4j for absolute performance
    • Style Overview
    • Distributed session on IMDG
    • Hybrid Serverless Modularized Monolithic
    • Kafka - Event Sourcing and CQRS
    • REST - Representational state transfer
    • Web Server with Light
    • Websocket with Light
    • Spring Boot Integration
    • Single Page Application
    • GraphQL - A query language for your API
    • Light IBM MQ
    • Light AWS Lambda
    • Chaos Monkey
  • Infrastructure Services
    • Service Overview
    • Light Proxy
    • Light Mesh
    • Light Router
    • Light Portal
    • Messaging Infrastructure
    • Centralized Logging
    • COVID-19
    • Light OAuth2
    • Metrics and Alerts
    • Config Server
    • Tokenization
    • Light Controller
  • Tool Chain
    • Tool Chain Overview
  • Utility Library
  • Service Consumer
    • Service Consumer
  • Development
    • Development Overview
  • Deployment
    • Deployment Overview
    • Frontend Backend
    • Linux Service
    • Windows Service
    • Install Eventuate on Windows
    • Secure API
    • Client vs light-router
    • Memory Limit
    • Deploy to Kubernetes
  • Benchmark
    • Benchmark Overview
  • Tutorial
    • Tutorial Overview
  • Troubleshooting
    • Troubleshoot
  • FAQ
    • FAQ Overview
  • Milestones
  • Contribute
    • Contribute to Light
    • Development
    • Documentation
    • Example
    • Tutorial
“OAuth2 Console” was last updated: May 23, 2019: fixes #90 add oauth2-console step in the local light-portal tutorial (5dd2cee)
Improve this page
  • News
  • Docs
  • Community
  • Reddit
  • GitHub
  • About Light
  • Getting Started
  • Architecture
  • Design
  • Cross-Cutting Concerns
  • API Styles
  • Infrastructure Services
  • Tool Chain
  • Utility Library
  • Service Consumer
  • Development
  • Deployment
  • Benchmark
  • Tutorial
  • Troubleshooting
  • FAQ
  • Milestones
  • Contribute