Skip to content

Conversation

@mariusae
Copy link
Collaborator

The old runtimes are no longer supported, and App Engine does not permit
creating or updating go1 projects.

This change introduces support of the go111 runtime. Newer runtimes no
longer support login: handlers.

mariusae and others added 2 commits November 13, 2019 12:08
The old runtimes are no longer supported, and App Engine does not permit
creating or updating go1 projects.

This change introduces support of the go111 runtime. Newer runtimes no
longer support login: handlers.
@rsc
Copy link
Owner

rsc commented Nov 14, 2019

I'm worried about the loss of login. I notice login: admin is still in the yaml file?
And if we lose login then how do we authenticate instead?

@mariusae
Copy link
Collaborator Author

go111 supports login still (it's technically "deprecated" within go111), and it works the same. go112+ do not. In that case, we have to use the sign-in APIs directly. I left that as future work.

Note that this change strictly improves on the current situation since the go1 runtime is no longer deployable in App Engine, go111 is.

mariusae and others added 4 commits November 14, 2019 10:01
tiddlywiki: upgrade to 5.1.21
The old runtimes are no longer supported, and App Engine does not permit
creating or updating go1 projects.

This change introduces support of the go111 runtime. Newer runtimes no
longer support login: handlers.
@sevki
Copy link

sevki commented Nov 15, 2019

could adding support for https://github.com/duo-labs/webauthn solve this problem for go 1.12+?

@philips
Copy link

philips commented May 28, 2020

See #7 for a replacement with Google's Identity Aware Proxy

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants