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

Improvement: alternative to Identity Certificate falling back to self-issued certificate #556

Open
sdsantos opened this issue Feb 8, 2022 · 1 comment · May be fixed by #726
Open

Improvement: alternative to Identity Certificate falling back to self-issued certificate #556

sdsantos opened this issue Feb 8, 2022 · 1 comment · May be fixed by #726
Labels
enhancement New feature or request

Comments

@sdsantos
Copy link
Collaborator

sdsantos commented Feb 8, 2022

Describe the problem

Sometimes the Gateway app does not have an Identity Certificate available. For example, while the initial registration with the public gateway wasn't concluded, or a Certificate expires and we haven't been able to renew it. Right now we fall back to a self-signed certificate, but that only works to communicate with the Public Gateway, and not for the rest of the uses the Identity Certificate has.

Describe the solution you'd like

Instead of just falling back to and storing a self-signed certificate, we should just create one for registration. And all other code that requires an Identity Certificate should be able to handle not having one (usually will mean not doing anything). Maybe we could even communicate to the user that the Gateway is not able to function fully until it registers again.

@sdsantos sdsantos added the enhancement New feature or request label Feb 8, 2022
@gnarea
Copy link
Member

gnarea commented Mar 30, 2022

We should also get rid of our hardcoded copy of frankfurt.relaycorp.cloud's certificate when we fix this:

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
Status: In Progress
Development

Successfully merging a pull request may close this issue.

2 participants