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

Clarify DB schema requirements for NAVER WORKS OAuth

Browse Source 
- Add naverworks_workspace table requirement
- Clarify token storage necessity (only for API usage)
- Note difference between login-only vs API usage scenarios
This commit is contained in:
happybell80 2025-09-17 21:18:35 +09:00
parent 5d91cb58f8
commit 4e82d17342
1 changed files with 4 additions and 1 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

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

@ -161,7 +161,10 @@
- **기존 user 테이블 활용** (SQLAlchemy: `__tablename__ = "user"`):
- oauth_provider="naverworks"
- oauth_id={NAVER WORKS userId}
- **신규 테이블**: `team.naverworks_token` (Service Account 토큰 저장용)
- **신규 테이블 필요**:
- `team.naverworks_workspace`: Workspace 정보 (Slack 패턴과 동일)
- `team.naverworks_token`: OIDC access_token/refresh_token 저장 (API 호출시 필수)
- 주의: 로그인만 할 경우 토큰 저장 불필요, API 사용시 필수
### 5.2 구현 플로우 (Slack 패턴 참조)