Closed MatthewJohn closed 11 months ago
bmaximuml
commented
1 year ago We're using terrareg with OIDC in a corporate environment in terraform. It would be very useful for us to be able to block all public access. Ideally, we'd have no public access, read access to any authenticated user, and write access to admins. Potentially an additional level of granularity to distinguish between write (can create / update modules) and admin (can admin users, can delete modules)
MatthewJohn
commented
1 year ago We're using terrareg with OIDC in a corporate environment in terraform. It would be very useful for us to be able to block all public access. Ideally, we'd have no public access, read access to any authenticated user, and write access to admins. Potentially an additional level of granularity to distinguish between write (can create / update modules) and admin (can admin users, can delete modules)
Excellent - I'll take a look into that at some point soon then :)
MatthewJohn
commented
12 months ago I've created a PR with these changes :) https://gitlab.dockstudios.co.uk/pub/terrareg/-/merge_requests/356
MatthewJohn
commented
11 months ago This has been released in v2.80.0 :)
MatthewJohn
commented
6 months ago Created gitlab issue: https://gitlab.dockstudios.co.uk/pub/terrareg/-/issues/503 gitlab-issue-id:503
I've realised quite a few people are using OpenIDC and SAML within corporate environments. There are a couple of tickets on the backlog (https://gitlab.dockstudios.co.uk/pub/terrareg/-/issues/392, https://gitlab.dockstudios.co.uk/pub/terrareg/-/issues/289) to enforce authentication (basically removing anonymous read access to Terrareg). This would also mean adding authentication when using Terraform.
I'm creating this ticket as a place for people to vote on it, to see if it's something that would be useful - so please give it a thumbs up, if it's something that's wanted :)
Matt