[FOLIO-2217] secure supertenant on kubernetes cluster Created: 20/Aug/19 Updated: 03/Jun/20 Resolved: 28/Aug/19 |
|
| Status: | Closed |
| Project: | FOLIO |
| Components: | None |
| Affects versions: | None |
| Fix versions: | None |
| Type: | Task | Priority: | P2 |
| Reporter: | Ian Hardy | Assignee: | Ian Hardy |
| Resolution: | Done | Votes: | 0 |
| Labels: | platform-backlog | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original estimate: | Not Specified | ||
| Issue links: |
|
||||||||
| Sprint: | CP: sprint 71 | ||||||||
| Story Points: | 1 | ||||||||
| Development Team: | Core: Platform | ||||||||
| Description |
|
supertenant on kubernetes should be secured (use okapi-secure role) |
| Comments |
| Comment by Ian Hardy [ 28/Aug/19 ] |
|
Secured supertenant on okapi-default namespace (okapi-default.ci.folio.org). Shared credentials w/ID deveops people, and will add to password store. There are other okapi's running in the okapi-demo and okapi-testing namespace which I think would be best to remove and redeploy w/security if needed. |