daita-technologies/backend

auth.daita.tech for github (prod and dev environment)

Closed this issue · 9 comments

well basically auth.daita.tech points to a Cloudfront link. Not sure which AWS account, however - so if we use one Cloudfront link for dev & prod we need to make sure this is in the prod environment for safety reasons! Otherwise, I propose to separate those two.

auth.daita.tech currently points to d2qifbh3avv0xt.cloudfront.net. So the main question is whether we use another CloudFront link from the AWS Prod Account for the production environment for auth.daita.tech and use e.g. authdev.daita.tech for the dev environment or we use the same link for both environments (which will limit our capability of breaking things here!)? I would prefer to segregate both.

since it's in the same context here, we need OAuth app for the production application (I will call it simply "DAITA Platform"). Let me know what I should put here and I will set it up accordingly in GitHub:
image

image

This issue here need to be resolved before the release.

For the record:

  • Homepage URL: https://auth.daita.tech/login
  • Authorization callback URL: https://app.daita.tech/oauth2/idpresponse

what's the status here @BEdaita?

Now , All url on app.daita.tech (auth.daita.tech) is set on production ,I will move dev enviroment (devauth.daita.tech) to dev account of aws because cognito app is just set one custom url. Thank you.

ok thx - can you confirm here quickly once this is done.

after production release , We move to dev enviorment , I will send to you the credential url of dev enviroment.

so this issue will resolved after the production release right? one thing that you must fix before is the switching to the Prod OAuth App from GitHub. Currently for app.daita.tech it's still on the dev version:
image

so this issue will resolved after the production release right? one thing that you must fix before is the switching to the Prod OAuth App from GitHub. Currently for app.daita.tech it's still on the dev version: image

The above issue has been resolved. The remaining open point is that after the production release, we will make devauth.daita.tech URL in the AWS Dev account and configure it properly in Cloudflare. I keep this issue open for the moment.