mirror of
https://github.com/google/nomulus.git
synced 2025-05-16 09:27:16 +02:00
c6d47d8d00
* Use the server host when creating the registry lock verification URL The app doesn't know about any external configuration that may point to this app, so there's no way of finding out that, for instance, registry.google points to the app. Thus, we have to use what the user gives us so that, in our case, the registry-lock verification emails can point to https://registry.google/registry-lock-verify instead of https://domain-registry.appspot.com/registry-lock-verify. The former is used by clients / users to authenticate, and unfortunately authenticating on registry.google does not give authentication to domain-registry.apspot.com. Tested using the RDAP code that uses getServerName() -- in that case, if you access registry.google/rdap/<>, it uses registry.google in the URLs but if you use domain-registry.appspot.com/rdap/<>, it uses domain-registry.appspot.com in the URLs. Relatedly, frontend_config_prod-appengine.asciiproto in Piper is what configures registry.google to point to domain-registry.appspot.com |
||
|---|---|---|
| .. | ||
| gradle/dependency-locks | ||
| src | ||
| WEB-INF/appengine-generated | ||
| build.gradle | ||
| Dockerfile | ||
| karma.conf.js | ||