Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

feat: authentication autorization strategy with next auth and gqlgen #49

Conversation

42atomys
Copy link
Owner

@42atomys 42atomys commented Apr 9, 2022

Relative Issues: #48

Describe the pull request
Adding a fully Authorization and Authentication workflow on https://github.com/42Atomys/stud42/labels/aspect%2Fbackend%20%F0%9F%92%BB and https://github.com/42Atomys/stud42/labels/aspect%2Finterface%20%F0%9F%95%B9 .

Provide a fully documented and workload experience for futures contributors https://github.com/42Atomys/stud42/labels/aspect%2Fdex%20%F0%9F%A4%96

Checklist

  • I have linked the relative issue to this pull request
  • I have made the modifications or added tests related to my PR
  • I have added/updated the documentation for my RP
  • I put my PR in Ready for Review only when all the checklist is checked

Breaking changes ?
yes/no

Additional context

@42atomys 42atomys added aspect/documentation 📚 Improvements or additions to documentation aspect/backend 💻 Concerns the backend code in the repository aspect/interface 🕹 Concerns end-users' experience with the software aspect/dex 🤖 Concerns developers' experience with the codebase labels Apr 9, 2022
@42atomys 42atomys added this to the 3.0 Beta Release 👷 milestone Apr 9, 2022
@42atomys 42atomys self-assigned this Apr 9, 2022
@42atomys 42atomys linked an issue Apr 9, 2022 that may be closed by this pull request
@42atomys 42atomys merged commit ba37d3b into main Apr 13, 2022
@42atomys 42atomys deleted the 48-feat-authentication-autorization-strategy-with-next-auth-and-gqlgen branch April 13, 2022 13:09
42atomys added a commit that referenced this pull request Apr 21, 2022
…49)

* feat: Use gqlgen and ent generator

* feat(authz): Add fully fonctionnal Authentication & Network Policy Authorization workflow

* fix: Remove port from remote addr and add some debug data

* chore: Change the name of the internal mutation

* feat(interface): Add TypeSafe GQL strategy woth GraphQL Code Generator

* feat: Add Sentry, not tested in production

* feat: Add Authentication with DUO & GITHUB, login workflow, secure page and auto redirect

* chore: Run yarn

* chore: Add Generation of code in CI

* feat: Setup Apollo with Baerer token

* chore: Update CI version to Go 1.18

* fix: Resolve UUID test version

* fix: Issue sponsors

* fix: Assign Sponsor only when user is sponsor

* fix: Secure usage of Graphql api env var
42atomys added a commit that referenced this pull request Nov 12, 2022
…49)

* feat: Use gqlgen and ent generator

* feat(authz): Add fully fonctionnal Authentication & Network Policy Authorization workflow

* fix: Remove port from remote addr and add some debug data

* chore: Change the name of the internal mutation

* feat(interface): Add TypeSafe GQL strategy woth GraphQL Code Generator

* feat: Add Sentry, not tested in production

* feat: Add Authentication with DUO & GITHUB, login workflow, secure page and auto redirect

* chore: Run yarn

* chore: Add Generation of code in CI

* feat: Setup Apollo with Baerer token

* chore: Update CI version to Go 1.18

* fix: Resolve UUID test version

* fix: Issue sponsors

* fix: Assign Sponsor only when user is sponsor

* fix: Secure usage of Graphql api env var
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
aspect/backend 💻 Concerns the backend code in the repository aspect/dex 🤖 Concerns developers' experience with the codebase aspect/documentation 📚 Improvements or additions to documentation aspect/interface 🕹 Concerns end-users' experience with the software
Projects
Status: Done 🎉
Development

Successfully merging this pull request may close these issues.

feat: Authentication & Autorization strategy with next-auth and gqlgen
1 participant