closed-social
/
gitea
3
0
Fork 0
Code Issues 0 Pull Requests 0 Projects 0 Releases 0 Wiki Activity
You can not select more than 25 topics Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.
5830 Commits
2 Branches
178 MiB
Tree: 183da4c2c1
Branches Tags
${ item.name }
Create branch ${ searchTerm }
from '183da4c2c1'
${ noResults }
gitea/templates/user/settings/account_link.tmpl

44 lines
1.3 KiB
Raw Normal View History

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)
7 years ago
​
Cleaner ui for admin, repo settings, and user settings page (#1269) (#1270)
7 years ago
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)
7 years ago
Cleaner ui for admin, repo settings, and user settings page (#1269) (#1270)
7 years ago
​
​
​
​
​
​
​
​
​
​
Simplify settings pages with item list (#1389) * Remove point column on ssh key setting page * Remove un-used css * Some cleaning * Use octicon-key
7 years ago
​
Cleaner ui for admin, repo settings, and user settings page (#1269) (#1270)
7 years ago
​
​
Simplify settings pages with item list (#1389) * Remove point column on ssh key setting page * Remove un-used css * Some cleaning * Use octicon-key
7 years ago
​
​
​
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)
7 years ago
​
Cleaner ui for admin, repo settings, and user settings page (#1269) (#1270)
7 years ago
​
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)
7 years ago
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
 
  1. {{template "base/head" .}}

  2. <div class="user settings account_link">

  3. 	{{template "user/settings/navbar" .}}

  4. 	<div class="ui container">

  5. 		{{template "base/alert" .}}

  6. 		<h4 class="ui top attached header">

  7. 			{{.i18n.Tr "settings.manage_account_links"}}

  8. 		</h4>

  9. 		<div class="ui attached segment">

  10. 			<div class="ui key list">

  11. 				<div class="item">

  12. 					{{.i18n.Tr "settings.manage_account_links_desc"}}

  13. 				</div>

  14. 				{{if .AccountLinks}}

  15. 				{{range $loginSource, $provider := .AccountLinks}}

  16. 					<div class="item">

  17. 					    <div class="right floated content">

  18. 								<button class="ui red tiny button delete-button" data-url="{{$.Link}}" data-id="{{$loginSource.ID}}">

  19. 									{{$.i18n.Tr "settings.delete_key"}}

  20. 								</button>

  21. 					    </div>

  22. 							<div class="content">

  23. 								<strong>{{$provider}}</strong>

  24. 								{{if $loginSource.IsActived}}<span class="text red">{{$.i18n.Tr "settings.active"}}</span>{{end}}

  25. 							</div>

  26. 					</div>

  27. 				{{end}}

  28. 				{{end}}

  29. 			</div>

  30. 		</div>

  31. 	</div>

  32. </div>

  33. 

  34. <div class="ui small basic delete modal">

  35. 	<div class="ui icon header">

  36. 		<i class="trash icon"></i>

  37. 		{{.i18n.Tr "settings.remove_account_link"}}

  38. 	</div>

  39. 	<div class="content">

  40. 		<p>{{.i18n.Tr "settings.remove_account_link_desc"}}</p>

  41. 	</div>

  42. 	{{template "base/delete_modal_actions" .}}

  43. </div>

  44. {{template "base/footer" .}}