How jasontsai123/oauthdevelopmentpractice works
Project type and purpose
• This is a full-stack ASP.NET Core MVC web application that implements OAuth 2.0 user flows for LINE Login and LINE Notify.
• It provides:
• User authentication via LINE Login
• Subscription, notification, and unsubscription via LINE Notify
• An admin UI to send broadcast messages
• Persistence with EF Core using an in-memory SQLite database (with scaffolding via Migrations).
File structure
• Top-level:
• WebSite/ – the main MVC app
– Controllers/ – HTTP endpoints for Login, Logout, Home, Admin, LineNotify
– Models/ – view models & DTOs (ErrorViewModel, SendNotifyMessage, etc.)
– Repositories/ – encapsulate calls to external LINE APIs and data-access for subscribers
– Database/ – EF Core DbContext (MemberContext.cs)
– Migrations/ – EF Core model snapshot and migration files
– Views/ – Razor views for UI
– wwwroot/ – static assets (CSS, JS, images, Bootstrap, jQuery)
– appsettings.json & launchSettings.json – configuration
– Dockerfile & .dockerignore – containerization
• WebSiteTest/ – unit tests for the subscriber repository
• identifier.sqlite – local SQLite DB file
README for additional insights
• Describes OAuth flows for both LINE Notify and LINE Login:
• GET /oauth/authorize → callback → POST /oauth/token → API calls
• Key external dependencies: notify-bot.line.me and access.line.me endpoints
• Highlights that Notify and Login are implemented as independent “platform” modules.