ivada-infra/DOCS
3
0
Fork 0
Code Issues 1 Pull Requests 5 Actions Packages Projects Releases Wiki Activity

Update DB schema for two-phase implementation plan

Browse Source 
Phase 1: Login only with existing user table
Phase 2: Passport with workspace and token tables for API access
This commit is contained in:
happybell80 2025-09-17 21:29:15 +09:00
parent 911272a42e
commit 42188eecf0
1 changed files with 4 additions and 4 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

8
ideas/250916_네이버웍스_캘린더_API_연동_가이드.md
View File

@ -159,15 +159,15 @@
- **`nginx-infra`**: `/auth/naverworks`, `/api/naverworks` 라우팅 설정 - **`nginx-infra`**: `/auth/naverworks`, `/api/naverworks` 라우팅 설정
#### DB 스키마 #### DB 스키마
- **로그인만 구현 (Phase 1)**: - **Phase 1: 로그인 구현** (현재):
- 기존 `user` 테이블만 사용 - 기존 `user` 테이블만 사용
- oauth_provider="naverworks" - oauth_provider="naverworks"
- oauth_id={userinfo.sub} - oauth_id={userinfo.sub}
- 신규 테이블 불필요
- **API 사용시 추가 필요 (Phase 2)**: - **Phase 2: Passport 구현** (다음):
- `team.naverworks_workspace`: Workspace 정보 - `team.naverworks_workspace`: Workspace 정보 저장
- `team.naverworks_token`: access_token/refresh_token 저장 - `team.naverworks_token`: access_token/refresh_token 저장
- 메일/캘린더 API 접근용
### 5.2 구현 플로우 (Slack 패턴 참조) ### 5.2 구현 플로우 (Slack 패턴 참조)