This website requires JavaScript.
Explore
CI
Help
Sign In
forgejo.dev
/
forgejo
Watch
2
Star
0
Fork
You've already forked forgejo
0
mirror of
https://codeberg.org/forgejo/forgejo.git
synced
2024-09-08 17:03:44 +00:00
Code
Issues
Projects
Releases
Packages
Wiki
Activity
7d8f9d1c46
forgejo
/
templates
/
user
/
auth
/
signin.tmpl
4 lines
96 B
Cheetah
Raw
Normal View
History
Unescape
Escape
new sign in page
2015-09-15 02:50:44 +00:00
{{template "base/head" .}}
Oauth2 consumer (#679) * initial stuff for oauth2 login, fails on: * login button on the signIn page to start the OAuth2 flow and a callback for each provider Only GitHub is implemented for now * show login button only when the OAuth2 consumer is configured (and activated) * create macaron group for oauth2 urls * prevent net/http in modules (other then oauth2) * use a new data sessions oauth2 folder for storing the oauth2 session data * add missing 2FA when this is enabled on the user * add password option for OAuth2 user , for use with git over http and login to the GUI * add tip for registering a GitHub OAuth application * at startup of Gitea register all configured providers and also on adding/deleting of new providers * custom handling of errors in oauth2 request init + show better tip * add ExternalLoginUser model and migration script to add it to database * link a external account to an existing account (still need to handle wrong login and signup) and remove if user is removed * remove the linked external account from the user his settings * if user is unknown we allow him to register a new account or link it to some existing account * sign up with button on signin page (als change OAuth2Provider structure so we can store basic stuff about providers) * from gorilla/sessions docs: "Important Note: If you aren't using gorilla/mux, you need to wrap your handlers with context.ClearHandler as or else you will leak memory!" (we're using gorilla/sessions for storing oauth2 sessions) * use updated goth lib that now supports getting the OAuth2 user if the AccessToken is still valid instead of re-authenticating (prevent flooding the OAuth2 provider)
2017-02-22 07:14:37 +00:00
{{template "user/auth/signin_inner" .}}
new sign in page
2015-09-15 02:50:44 +00:00
{{template "base/footer" .}}
Reference in a new issue
Copy permalink