mirror of
				https://gitee.com/gitea/gitea
				synced 2025-11-04 08:30:25 +08:00 
			
		
		
		
	Use [chi](https://github.com/go-chi/chi) instead of the forked [macaron](https://gitea.com/macaron/macaron). Since macaron and chi have conflicts with session share, this big PR becomes a have-to thing. According my previous idea, we can replace macaron step by step but I'm wrong. :( Below is a list of big changes on this PR. - [x] Define `context.ResponseWriter` interface with an implementation `context.Response`. - [x] Use chi instead of macaron, and also a customize `Route` to wrap chi so that the router usage is similar as before. - [x] Create different routers for `web`, `api`, `internal` and `install` so that the codes will be more clear and no magic . - [x] Use https://github.com/unrolled/render instead of macaron's internal render - [x] Use https://github.com/NYTimes/gziphandler instead of https://gitea.com/macaron/gzip - [x] Use https://gitea.com/go-chi/session which is a modified version of https://gitea.com/macaron/session and removed `nodb` support since it will not be maintained. **BREAK** - [x] Use https://gitea.com/go-chi/captcha which is a modified version of https://gitea.com/macaron/captcha - [x] Use https://gitea.com/go-chi/cache which is a modified version of https://gitea.com/macaron/cache - [x] Use https://gitea.com/go-chi/binding which is a modified version of https://gitea.com/macaron/binding - [x] Use https://github.com/go-chi/cors instead of https://gitea.com/macaron/cors - [x] Dropped https://gitea.com/macaron/i18n and make a new one in `code.gitea.io/gitea/modules/translation` - [x] Move validation form structs from `code.gitea.io/gitea/modules/auth` to `code.gitea.io/gitea/modules/forms` to avoid dependency cycle. - [x] Removed macaron log service because it's not need any more. **BREAK** - [x] All form structs have to be get by `web.GetForm(ctx)` in the route function but not as a function parameter on routes definition. - [x] Move Git HTTP protocol implementation to use routers directly. - [x] Fix the problem that chi routes don't support trailing slash but macaron did. - [x] `/api/v1/swagger` now will be redirect to `/api/swagger` but not render directly so that `APIContext` will not create a html render. Notices: - Chi router don't support request with trailing slash - Integration test `TestUserHeatmap` maybe mysql version related. It's failed on my macOS(mysql 5.7.29 installed via brew) but succeed on CI. Co-authored-by: 6543 <6543@obermui.de>
		
			
				
	
	
		
			41 lines
		
	
	
		
			1.4 KiB
		
	
	
	
		
			Go
		
	
	
	
	
	
			
		
		
	
	
			41 lines
		
	
	
		
			1.4 KiB
		
	
	
	
		
			Go
		
	
	
	
	
	
// Copyright 2019 The Gitea Authors. All rights reserved.
 | 
						|
// Use of this source code is governed by a MIT-style
 | 
						|
// license that can be found in the LICENSE file.
 | 
						|
 | 
						|
package sso
 | 
						|
 | 
						|
import (
 | 
						|
	"net/http"
 | 
						|
 | 
						|
	"code.gitea.io/gitea/models"
 | 
						|
	"code.gitea.io/gitea/modules/middlewares"
 | 
						|
	"code.gitea.io/gitea/modules/session"
 | 
						|
)
 | 
						|
 | 
						|
// DataStore represents a data store
 | 
						|
type DataStore middlewares.DataStore
 | 
						|
 | 
						|
// SessionStore represents a session store
 | 
						|
type SessionStore session.Store
 | 
						|
 | 
						|
// SingleSignOn represents a SSO authentication method (plugin) for HTTP requests.
 | 
						|
type SingleSignOn interface {
 | 
						|
	// Init should be called exactly once before using any of the other methods,
 | 
						|
	// in order to allow the plugin to allocate necessary resources
 | 
						|
	Init() error
 | 
						|
 | 
						|
	// Free should be called exactly once before application closes, in order to
 | 
						|
	// give chance to the plugin to free any allocated resources
 | 
						|
	Free() error
 | 
						|
 | 
						|
	// IsEnabled checks if the current SSO method has been enabled in settings.
 | 
						|
	IsEnabled() bool
 | 
						|
 | 
						|
	// VerifyAuthData tries to verify the SSO authentication data contained in the request.
 | 
						|
	// If verification is successful returns either an existing user object (with id > 0)
 | 
						|
	// or a new user object (with id = 0) populated with the information that was found
 | 
						|
	// in the authentication data (username or email).
 | 
						|
	// Returns nil if verification fails.
 | 
						|
	VerifyAuthData(http *http.Request, w http.ResponseWriter, store DataStore, sess SessionStore) *models.User
 | 
						|
}
 |