forked from baron/baron-sso
문서화 및 로직 정리.
This commit is contained in:
@@ -18,6 +18,15 @@
|
||||
- **Method**: Enchanted Link only (No Magic Link).
|
||||
- **Requirement**: Invisible to end-users (White-labeling).
|
||||
|
||||
## Core Scenarios
|
||||
1. **Same Browser SSO**: Access apps from Baron SSO launcher (logged in state).
|
||||
2. **Cross-Device Auth**: Approve PC login via Mobile Baron SSO app (Enchanted Link required).
|
||||
3. **Clean Login**: Email/SMS initial login. Future: OTP, MFA.
|
||||
|
||||
## Future Milestones
|
||||
- **Passkey Support**: Expanded seamless auth for Scenario 2 & 3.
|
||||
- **MFA Expansion**: OTP integration.
|
||||
|
||||
## Coding Standards
|
||||
- **Go**: Follow standard Go project layout (`cmd`, `internal`, `pkg`). Use Clean Architecture principles where appropriate. Handle errors explicitly.
|
||||
- **Flutter**: Use Riverpod for state management. Separate UI (Widgets) from Business Logic (Providers/Repositories).
|
||||
|
||||
Reference in New Issue
Block a user