[FOLIO-1827] Enable okapi-secure role on aws builds Created: 26/Feb/19  Updated: 03/Jun/20  Resolved: 25/Mar/19

Status: Closed
Project: FOLIO
Components: None
Affects versions: None
Fix versions: None

Type: Task Priority: P3
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:
Blocks
is blocked by FOLIO-1799 add Okapi authentication hook to exis... Closed
Sprint: Core: Platform - Sprint 58, Core: Platform - Sprint 59
Story Points: 2
Development Team: Core: Platform

 Description   

Enable the Okapi secure role (built in FOLIO-1798 Closed ) for aws builds to secure installation. Other roles that talk to Okapi need to be modified to authenticate ( FOLIO-1799 Closed ).



 Comments   
Comment by Ian Hardy [ 08/Mar/19 ]

Plan to complete:

  • -Test build secured backend testing -
  • test builds for frontend
  • Merge changed in folio-infrastructure to master (Monday 3/11)
  • Allow scheduled builds to occur Monday night, secured builds ready Tuesday
Comment by Ian Hardy [ 25/Mar/19 ]

secured okapi on snapshot and testing. Credentials are in the defaults of the okapi-secure role:

https://github.com/folio-org/folio-ansible/blob/master/roles/okapi-secure/defaults/main.yml

Can be set to something private if needed.

prs for securing:

snapshot: https://github.com/folio-org/folio-infrastructure/pull/83
testing: https://github.com/folio-org/folio-infrastructure/pull/84

Generated at Thu Feb 08 23:16:11 UTC 2024 using Jira 1001.0.0-SNAPSHOT#100246-sha1:7a5c50119eb0633d306e14180817ddef5e80c75d.