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

Clarify DB requirements for phased implementation

Browse Source 
- Phase 1 (login only): Use existing user table, no new tables needed
- Phase 2 (API usage): Add workspace and token tables
This commit is contained in:
happybell80 2025-09-17 21:28:37 +09:00
parent 126f6a8770
commit 911272a42e
1 changed files with 8 additions and 6 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

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

@ -159,13 +159,15 @@
- **`nginx-infra`**: `/auth/naverworks`, `/api/naverworks` 라우팅 설정 - **`nginx-infra`**: `/auth/naverworks`, `/api/naverworks` 라우팅 설정
#### DB 스키마 #### DB 스키마
- **기존 user 테이블 활용** (SQLAlchemy: `__tablename__ = "user"`): - **로그인만 구현 (Phase 1)**:
- 기존 `user` 테이블만 사용
- oauth_provider="naverworks" - oauth_provider="naverworks"
- oauth_id={NAVER WORKS userId} - oauth_id={userinfo.sub}
- **신규 테이블 필요**: - 신규 테이블 불필요
- `team.naverworks_workspace`: Workspace 정보 (Slack 패턴과 동일)
- `team.naverworks_token`: OIDC access_token/refresh_token 저장 (API 호출시 필수) - **API 사용시 추가 필요 (Phase 2)**:
- 주의: 로그인만 할 경우 토큰 저장 불필요, API 사용시 필수 - `team.naverworks_workspace`: Workspace 정보
- `team.naverworks_token`: access_token/refresh_token 저장
### 5.2 구현 플로우 (Slack 패턴 참조) ### 5.2 구현 플로우 (Slack 패턴 참조)