2019-11-22 18:33:31 -05:00
|
|
|
// Copyright 2014 The Gogs Authors. All rights reserved.
|
|
|
|
// Copyright 2019 The Gitea Authors. All rights reserved.
|
2022-11-27 13:20:29 -05:00
|
|
|
// SPDX-License-Identifier: MIT
|
2019-11-22 18:33:31 -05:00
|
|
|
|
2021-06-09 12:53:16 -05:00
|
|
|
package auth
|
2019-11-22 18:33:31 -05:00
|
|
|
|
|
|
|
import (
|
2021-01-05 08:05:40 -05:00
|
|
|
"net/http"
|
2019-11-22 18:33:31 -05:00
|
|
|
"strings"
|
|
|
|
|
2022-08-24 21:31:57 -05:00
|
|
|
auth_model "code.gitea.io/gitea/models/auth"
|
2021-11-24 04:49:20 -05:00
|
|
|
user_model "code.gitea.io/gitea/models/user"
|
2019-11-22 18:33:31 -05:00
|
|
|
"code.gitea.io/gitea/modules/base"
|
|
|
|
"code.gitea.io/gitea/modules/log"
|
|
|
|
"code.gitea.io/gitea/modules/setting"
|
|
|
|
"code.gitea.io/gitea/modules/timeutil"
|
2021-05-15 10:32:09 -05:00
|
|
|
"code.gitea.io/gitea/modules/web/middleware"
|
2019-11-22 18:33:31 -05:00
|
|
|
)
|
|
|
|
|
|
|
|
// Ensure the struct implements the interface.
|
|
|
|
var (
|
2021-07-24 05:16:34 -05:00
|
|
|
_ Method = &Basic{}
|
|
|
|
_ Named = &Basic{}
|
2019-11-22 18:33:31 -05:00
|
|
|
)
|
|
|
|
|
2021-11-20 10:33:18 -05:00
|
|
|
// BasicMethodName is the constant name of the basic authentication method
|
|
|
|
const BasicMethodName = "basic"
|
|
|
|
|
2021-06-09 12:53:16 -05:00
|
|
|
// Basic implements the Auth interface and authenticates requests (API requests
|
2019-11-22 18:33:31 -05:00
|
|
|
// only) by looking for Basic authentication data or "x-oauth-basic" token in the "Authorization"
|
|
|
|
// header.
|
2022-01-20 12:46:10 -05:00
|
|
|
type Basic struct{}
|
2019-11-22 18:33:31 -05:00
|
|
|
|
2021-06-09 12:53:16 -05:00
|
|
|
// Name represents the name of auth method
|
|
|
|
func (b *Basic) Name() string {
|
2021-11-20 10:33:18 -05:00
|
|
|
return BasicMethodName
|
2021-06-09 12:53:16 -05:00
|
|
|
}
|
|
|
|
|
|
|
|
// Verify extracts and validates Basic data (username and password/token) from the
|
2019-11-22 18:33:31 -05:00
|
|
|
// "Authorization" header of the request and returns the corresponding user object for that
|
|
|
|
// name/token on successful validation.
|
|
|
|
// Returns nil if header is empty or validation fails.
|
refactor auth interface to return error when verify failure (#22119)
This PR changed the Auth interface signature from
`Verify(http *http.Request, w http.ResponseWriter, store DataStore, sess
SessionStore) *user_model.User`
to
`Verify(http *http.Request, w http.ResponseWriter, store DataStore, sess
SessionStore) (*user_model.User, error)`.
There is a new return argument `error` which means the verification
condition matched but verify process failed, we should stop the auth
process.
Before this PR, when return a `nil` user, we don't know the reason why
it returned `nil`. If the match condition is not satisfied or it
verified failure? For these two different results, we should have
different handler. If the match condition is not satisfied, we should
try next auth method and if there is no more auth method, it's an
anonymous user. If the condition matched but verify failed, the auth
process should be stop and return immediately.
This will fix #20563
Co-authored-by: KN4CK3R <admin@oldschoolhack.me>
Co-authored-by: Jason Song <i@wolfogre.com>
2022-12-28 00:53:28 -05:00
|
|
|
func (b *Basic) Verify(req *http.Request, w http.ResponseWriter, store DataStore, sess SessionStore) (*user_model.User, error) {
|
2021-05-15 10:32:09 -05:00
|
|
|
// Basic authentication should only fire on API, Download or on Git or LFSPaths
|
2022-03-30 03:42:47 -05:00
|
|
|
if !middleware.IsAPIPath(req) && !isContainerPath(req) && !isAttachmentDownload(req) && !isGitRawReleaseOrLFSPath(req) {
|
refactor auth interface to return error when verify failure (#22119)
This PR changed the Auth interface signature from
`Verify(http *http.Request, w http.ResponseWriter, store DataStore, sess
SessionStore) *user_model.User`
to
`Verify(http *http.Request, w http.ResponseWriter, store DataStore, sess
SessionStore) (*user_model.User, error)`.
There is a new return argument `error` which means the verification
condition matched but verify process failed, we should stop the auth
process.
Before this PR, when return a `nil` user, we don't know the reason why
it returned `nil`. If the match condition is not satisfied or it
verified failure? For these two different results, we should have
different handler. If the match condition is not satisfied, we should
try next auth method and if there is no more auth method, it's an
anonymous user. If the condition matched but verify failed, the auth
process should be stop and return immediately.
This will fix #20563
Co-authored-by: KN4CK3R <admin@oldschoolhack.me>
Co-authored-by: Jason Song <i@wolfogre.com>
2022-12-28 00:53:28 -05:00
|
|
|
return nil, nil
|
2021-05-15 10:32:09 -05:00
|
|
|
}
|
|
|
|
|
2021-01-05 08:05:40 -05:00
|
|
|
baHead := req.Header.Get("Authorization")
|
2019-11-22 18:33:31 -05:00
|
|
|
if len(baHead) == 0 {
|
refactor auth interface to return error when verify failure (#22119)
This PR changed the Auth interface signature from
`Verify(http *http.Request, w http.ResponseWriter, store DataStore, sess
SessionStore) *user_model.User`
to
`Verify(http *http.Request, w http.ResponseWriter, store DataStore, sess
SessionStore) (*user_model.User, error)`.
There is a new return argument `error` which means the verification
condition matched but verify process failed, we should stop the auth
process.
Before this PR, when return a `nil` user, we don't know the reason why
it returned `nil`. If the match condition is not satisfied or it
verified failure? For these two different results, we should have
different handler. If the match condition is not satisfied, we should
try next auth method and if there is no more auth method, it's an
anonymous user. If the condition matched but verify failed, the auth
process should be stop and return immediately.
This will fix #20563
Co-authored-by: KN4CK3R <admin@oldschoolhack.me>
Co-authored-by: Jason Song <i@wolfogre.com>
2022-12-28 00:53:28 -05:00
|
|
|
return nil, nil
|
2019-11-22 18:33:31 -05:00
|
|
|
}
|
|
|
|
|
2021-05-15 10:32:09 -05:00
|
|
|
auths := strings.SplitN(baHead, " ", 2)
|
2021-11-12 18:27:18 -05:00
|
|
|
if len(auths) != 2 || (strings.ToLower(auths[0]) != "basic") {
|
refactor auth interface to return error when verify failure (#22119)
This PR changed the Auth interface signature from
`Verify(http *http.Request, w http.ResponseWriter, store DataStore, sess
SessionStore) *user_model.User`
to
`Verify(http *http.Request, w http.ResponseWriter, store DataStore, sess
SessionStore) (*user_model.User, error)`.
There is a new return argument `error` which means the verification
condition matched but verify process failed, we should stop the auth
process.
Before this PR, when return a `nil` user, we don't know the reason why
it returned `nil`. If the match condition is not satisfied or it
verified failure? For these two different results, we should have
different handler. If the match condition is not satisfied, we should
try next auth method and if there is no more auth method, it's an
anonymous user. If the condition matched but verify failed, the auth
process should be stop and return immediately.
This will fix #20563
Co-authored-by: KN4CK3R <admin@oldschoolhack.me>
Co-authored-by: Jason Song <i@wolfogre.com>
2022-12-28 00:53:28 -05:00
|
|
|
return nil, nil
|
2019-11-22 18:33:31 -05:00
|
|
|
}
|
|
|
|
|
|
|
|
uname, passwd, _ := base.BasicAuthDecode(auths[1])
|
|
|
|
|
|
|
|
// Check if username or password is a token
|
|
|
|
isUsernameToken := len(passwd) == 0 || passwd == "x-oauth-basic"
|
|
|
|
// Assume username is token
|
|
|
|
authToken := uname
|
|
|
|
if !isUsernameToken {
|
2021-05-09 11:04:53 -05:00
|
|
|
log.Trace("Basic Authorization: Attempting login for: %s", uname)
|
2019-11-22 18:33:31 -05:00
|
|
|
// Assume password is token
|
|
|
|
authToken = passwd
|
2021-05-09 11:04:53 -05:00
|
|
|
} else {
|
|
|
|
log.Trace("Basic Authorization: Attempting login with username as token")
|
2019-11-22 18:33:31 -05:00
|
|
|
}
|
|
|
|
|
|
|
|
uid := CheckOAuthAccessToken(authToken)
|
|
|
|
if uid != 0 {
|
2021-05-09 11:04:53 -05:00
|
|
|
log.Trace("Basic Authorization: Valid OAuthAccessToken for user[%d]", uid)
|
2019-11-22 18:33:31 -05:00
|
|
|
|
2022-12-02 21:48:26 -05:00
|
|
|
u, err := user_model.GetUserByID(req.Context(), uid)
|
2019-11-22 18:33:31 -05:00
|
|
|
if err != nil {
|
|
|
|
log.Error("GetUserByID: %v", err)
|
refactor auth interface to return error when verify failure (#22119)
This PR changed the Auth interface signature from
`Verify(http *http.Request, w http.ResponseWriter, store DataStore, sess
SessionStore) *user_model.User`
to
`Verify(http *http.Request, w http.ResponseWriter, store DataStore, sess
SessionStore) (*user_model.User, error)`.
There is a new return argument `error` which means the verification
condition matched but verify process failed, we should stop the auth
process.
Before this PR, when return a `nil` user, we don't know the reason why
it returned `nil`. If the match condition is not satisfied or it
verified failure? For these two different results, we should have
different handler. If the match condition is not satisfied, we should
try next auth method and if there is no more auth method, it's an
anonymous user. If the condition matched but verify failed, the auth
process should be stop and return immediately.
This will fix #20563
Co-authored-by: KN4CK3R <admin@oldschoolhack.me>
Co-authored-by: Jason Song <i@wolfogre.com>
2022-12-28 00:53:28 -05:00
|
|
|
return nil, err
|
2019-11-22 18:33:31 -05:00
|
|
|
}
|
2021-05-15 10:32:09 -05:00
|
|
|
|
|
|
|
store.GetData()["IsApiToken"] = true
|
refactor auth interface to return error when verify failure (#22119)
This PR changed the Auth interface signature from
`Verify(http *http.Request, w http.ResponseWriter, store DataStore, sess
SessionStore) *user_model.User`
to
`Verify(http *http.Request, w http.ResponseWriter, store DataStore, sess
SessionStore) (*user_model.User, error)`.
There is a new return argument `error` which means the verification
condition matched but verify process failed, we should stop the auth
process.
Before this PR, when return a `nil` user, we don't know the reason why
it returned `nil`. If the match condition is not satisfied or it
verified failure? For these two different results, we should have
different handler. If the match condition is not satisfied, we should
try next auth method and if there is no more auth method, it's an
anonymous user. If the condition matched but verify failed, the auth
process should be stop and return immediately.
This will fix #20563
Co-authored-by: KN4CK3R <admin@oldschoolhack.me>
Co-authored-by: Jason Song <i@wolfogre.com>
2022-12-28 00:53:28 -05:00
|
|
|
return u, nil
|
2019-11-22 18:33:31 -05:00
|
|
|
}
|
2021-05-15 10:32:09 -05:00
|
|
|
|
2022-08-24 21:31:57 -05:00
|
|
|
token, err := auth_model.GetAccessTokenBySHA(authToken)
|
2019-11-22 18:33:31 -05:00
|
|
|
if err == nil {
|
2021-05-09 11:04:53 -05:00
|
|
|
log.Trace("Basic Authorization: Valid AccessToken for user[%d]", uid)
|
2022-12-02 21:48:26 -05:00
|
|
|
u, err := user_model.GetUserByID(req.Context(), token.UID)
|
2020-04-14 13:32:03 -05:00
|
|
|
if err != nil {
|
|
|
|
log.Error("GetUserByID: %v", err)
|
refactor auth interface to return error when verify failure (#22119)
This PR changed the Auth interface signature from
`Verify(http *http.Request, w http.ResponseWriter, store DataStore, sess
SessionStore) *user_model.User`
to
`Verify(http *http.Request, w http.ResponseWriter, store DataStore, sess
SessionStore) (*user_model.User, error)`.
There is a new return argument `error` which means the verification
condition matched but verify process failed, we should stop the auth
process.
Before this PR, when return a `nil` user, we don't know the reason why
it returned `nil`. If the match condition is not satisfied or it
verified failure? For these two different results, we should have
different handler. If the match condition is not satisfied, we should
try next auth method and if there is no more auth method, it's an
anonymous user. If the condition matched but verify failed, the auth
process should be stop and return immediately.
This will fix #20563
Co-authored-by: KN4CK3R <admin@oldschoolhack.me>
Co-authored-by: Jason Song <i@wolfogre.com>
2022-12-28 00:53:28 -05:00
|
|
|
return nil, err
|
2019-11-22 18:33:31 -05:00
|
|
|
}
|
2020-04-14 13:32:03 -05:00
|
|
|
|
2019-11-22 18:33:31 -05:00
|
|
|
token.UpdatedUnix = timeutil.TimeStampNow()
|
2022-08-24 21:31:57 -05:00
|
|
|
if err = auth_model.UpdateAccessToken(token); err != nil {
|
2019-11-22 18:33:31 -05:00
|
|
|
log.Error("UpdateAccessToken: %v", err)
|
|
|
|
}
|
2021-05-15 10:32:09 -05:00
|
|
|
|
|
|
|
store.GetData()["IsApiToken"] = true
|
refactor auth interface to return error when verify failure (#22119)
This PR changed the Auth interface signature from
`Verify(http *http.Request, w http.ResponseWriter, store DataStore, sess
SessionStore) *user_model.User`
to
`Verify(http *http.Request, w http.ResponseWriter, store DataStore, sess
SessionStore) (*user_model.User, error)`.
There is a new return argument `error` which means the verification
condition matched but verify process failed, we should stop the auth
process.
Before this PR, when return a `nil` user, we don't know the reason why
it returned `nil`. If the match condition is not satisfied or it
verified failure? For these two different results, we should have
different handler. If the match condition is not satisfied, we should
try next auth method and if there is no more auth method, it's an
anonymous user. If the condition matched but verify failed, the auth
process should be stop and return immediately.
This will fix #20563
Co-authored-by: KN4CK3R <admin@oldschoolhack.me>
Co-authored-by: Jason Song <i@wolfogre.com>
2022-12-28 00:53:28 -05:00
|
|
|
return u, nil
|
2022-08-24 21:31:57 -05:00
|
|
|
} else if !auth_model.IsErrAccessTokenNotExist(err) && !auth_model.IsErrAccessTokenEmpty(err) {
|
2019-11-22 18:33:31 -05:00
|
|
|
log.Error("GetAccessTokenBySha: %v", err)
|
|
|
|
}
|
|
|
|
|
2021-05-15 10:32:09 -05:00
|
|
|
if !setting.Service.EnableBasicAuth {
|
refactor auth interface to return error when verify failure (#22119)
This PR changed the Auth interface signature from
`Verify(http *http.Request, w http.ResponseWriter, store DataStore, sess
SessionStore) *user_model.User`
to
`Verify(http *http.Request, w http.ResponseWriter, store DataStore, sess
SessionStore) (*user_model.User, error)`.
There is a new return argument `error` which means the verification
condition matched but verify process failed, we should stop the auth
process.
Before this PR, when return a `nil` user, we don't know the reason why
it returned `nil`. If the match condition is not satisfied or it
verified failure? For these two different results, we should have
different handler. If the match condition is not satisfied, we should
try next auth method and if there is no more auth method, it's an
anonymous user. If the condition matched but verify failed, the auth
process should be stop and return immediately.
This will fix #20563
Co-authored-by: KN4CK3R <admin@oldschoolhack.me>
Co-authored-by: Jason Song <i@wolfogre.com>
2022-12-28 00:53:28 -05:00
|
|
|
return nil, nil
|
2021-05-15 10:32:09 -05:00
|
|
|
}
|
2021-05-09 11:04:53 -05:00
|
|
|
|
2021-05-15 10:32:09 -05:00
|
|
|
log.Trace("Basic Authorization: Attempting SignIn for %s", uname)
|
2021-09-17 06:43:47 -05:00
|
|
|
u, source, err := UserSignIn(uname, passwd)
|
2021-05-15 10:32:09 -05:00
|
|
|
if err != nil {
|
2021-11-24 04:49:20 -05:00
|
|
|
if !user_model.IsErrUserNotExist(err) {
|
2021-05-15 10:32:09 -05:00
|
|
|
log.Error("UserSignIn: %v", err)
|
2019-11-22 18:33:31 -05:00
|
|
|
}
|
refactor auth interface to return error when verify failure (#22119)
This PR changed the Auth interface signature from
`Verify(http *http.Request, w http.ResponseWriter, store DataStore, sess
SessionStore) *user_model.User`
to
`Verify(http *http.Request, w http.ResponseWriter, store DataStore, sess
SessionStore) (*user_model.User, error)`.
There is a new return argument `error` which means the verification
condition matched but verify process failed, we should stop the auth
process.
Before this PR, when return a `nil` user, we don't know the reason why
it returned `nil`. If the match condition is not satisfied or it
verified failure? For these two different results, we should have
different handler. If the match condition is not satisfied, we should
try next auth method and if there is no more auth method, it's an
anonymous user. If the condition matched but verify failed, the auth
process should be stop and return immediately.
This will fix #20563
Co-authored-by: KN4CK3R <admin@oldschoolhack.me>
Co-authored-by: Jason Song <i@wolfogre.com>
2022-12-28 00:53:28 -05:00
|
|
|
return nil, err
|
2019-11-22 18:33:31 -05:00
|
|
|
}
|
|
|
|
|
2021-09-17 06:43:47 -05:00
|
|
|
if skipper, ok := source.Cfg.(LocalTwoFASkipper); ok && skipper.IsSkipLocalTwoFA() {
|
|
|
|
store.GetData()["SkipLocalTwoFA"] = true
|
|
|
|
}
|
|
|
|
|
2021-05-09 11:04:53 -05:00
|
|
|
log.Trace("Basic Authorization: Logged in user %-v", u)
|
|
|
|
|
refactor auth interface to return error when verify failure (#22119)
This PR changed the Auth interface signature from
`Verify(http *http.Request, w http.ResponseWriter, store DataStore, sess
SessionStore) *user_model.User`
to
`Verify(http *http.Request, w http.ResponseWriter, store DataStore, sess
SessionStore) (*user_model.User, error)`.
There is a new return argument `error` which means the verification
condition matched but verify process failed, we should stop the auth
process.
Before this PR, when return a `nil` user, we don't know the reason why
it returned `nil`. If the match condition is not satisfied or it
verified failure? For these two different results, we should have
different handler. If the match condition is not satisfied, we should
try next auth method and if there is no more auth method, it's an
anonymous user. If the condition matched but verify failed, the auth
process should be stop and return immediately.
This will fix #20563
Co-authored-by: KN4CK3R <admin@oldschoolhack.me>
Co-authored-by: Jason Song <i@wolfogre.com>
2022-12-28 00:53:28 -05:00
|
|
|
return u, nil
|
2019-11-22 18:33:31 -05:00
|
|
|
}
|