2019-04-25 04:52:08 +07:00
|
|
|
package handlers
|
|
|
|
|
|
|
|
import (
|
|
|
|
"fmt"
|
|
|
|
"net/url"
|
|
|
|
|
2021-08-11 08:04:35 +07:00
|
|
|
"github.com/authelia/authelia/v4/internal/duo"
|
|
|
|
"github.com/authelia/authelia/v4/internal/middlewares"
|
2019-04-25 04:52:08 +07:00
|
|
|
)
|
|
|
|
|
|
|
|
// SecondFactorDuoPost handler for sending a push notification via duo api.
|
|
|
|
func SecondFactorDuoPost(duoAPI duo.API) middlewares.RequestHandler {
|
|
|
|
return func(ctx *middlewares.AutheliaCtx) {
|
|
|
|
var requestBody signDuoRequestBody
|
|
|
|
err := ctx.ParseBody(&requestBody)
|
|
|
|
|
|
|
|
if err != nil {
|
2021-07-22 10:52:37 +07:00
|
|
|
handleAuthenticationUnauthorized(ctx, err, messageMFAValidationFailed)
|
2019-04-25 04:52:08 +07:00
|
|
|
return
|
|
|
|
}
|
|
|
|
|
|
|
|
userSession := ctx.GetSession()
|
2020-03-01 07:51:11 +07:00
|
|
|
remoteIP := ctx.RemoteIP().String()
|
|
|
|
|
|
|
|
ctx.Logger.Debugf("Starting Duo Push Auth Attempt for %s from IP %s", userSession.Username, remoteIP)
|
2019-04-25 04:52:08 +07:00
|
|
|
|
|
|
|
values := url.Values{}
|
|
|
|
// { username, ipaddr: clientIP, factor: "push", device: "auto", pushinfo: `target%20url=${targetURL}`}
|
|
|
|
values.Set("username", userSession.Username)
|
2020-03-01 07:51:11 +07:00
|
|
|
values.Set("ipaddr", remoteIP)
|
2019-04-25 04:52:08 +07:00
|
|
|
values.Set("factor", "push")
|
|
|
|
values.Set("device", "auto")
|
2020-05-06 02:35:32 +07:00
|
|
|
|
2019-04-25 04:52:08 +07:00
|
|
|
if requestBody.TargetURL != "" {
|
|
|
|
values.Set("pushinfo", fmt.Sprintf("target%%20url=%s", requestBody.TargetURL))
|
|
|
|
}
|
|
|
|
|
2020-03-01 07:51:11 +07:00
|
|
|
duoResponse, err := duoAPI.Call(values, ctx)
|
2019-04-25 04:52:08 +07:00
|
|
|
if err != nil {
|
2021-07-22 10:52:37 +07:00
|
|
|
handleAuthenticationUnauthorized(ctx, fmt.Errorf("Duo API errored: %s", err), messageMFAValidationFailed)
|
2019-04-25 04:52:08 +07:00
|
|
|
return
|
|
|
|
}
|
|
|
|
|
2020-03-01 07:51:11 +07:00
|
|
|
if duoResponse.Stat == "FAIL" {
|
|
|
|
if duoResponse.Code == 40002 {
|
|
|
|
ctx.Logger.Warnf("Duo Push Auth failed to process the auth request for %s from %s: %s (%s), error code %d. "+
|
|
|
|
"This error often occurs if you've not setup the username in the Admin Dashboard.",
|
|
|
|
userSession.Username, remoteIP, duoResponse.Message, duoResponse.MessageDetail, duoResponse.Code)
|
|
|
|
} else {
|
|
|
|
ctx.Logger.Warnf("Duo Push Auth failed to process the auth request for %s from %s: %s (%s), error code %d.",
|
|
|
|
userSession.Username, remoteIP, duoResponse.Message, duoResponse.MessageDetail, duoResponse.Code)
|
|
|
|
}
|
|
|
|
}
|
|
|
|
|
2020-05-02 23:20:40 +07:00
|
|
|
if duoResponse.Response.Result != testResultAllow {
|
2019-04-25 04:52:08 +07:00
|
|
|
ctx.ReplyUnauthorized()
|
|
|
|
return
|
|
|
|
}
|
|
|
|
|
2020-03-01 06:13:33 +07:00
|
|
|
err = ctx.Providers.SessionProvider.RegenerateSession(ctx.RequestCtx)
|
|
|
|
|
|
|
|
if err != nil {
|
2021-07-22 10:52:37 +07:00
|
|
|
handleAuthenticationUnauthorized(ctx, fmt.Errorf("Unable to regenerate session for user %s: %s", userSession.Username, err), messageMFAValidationFailed)
|
2020-03-01 06:13:33 +07:00
|
|
|
return
|
|
|
|
}
|
|
|
|
|
feat(oidc): add additional config options, accurate token times, and refactoring (#1991)
* This gives admins more control over their OIDC installation exposing options that had defaults before. Things like lifespans for authorize codes, access tokens, id tokens, refresh tokens, a option to enable the debug client messages, minimum parameter entropy. It also allows admins to configure the response modes.
* Additionally this records specific values about a users session indicating when they performed a specific authz factor so this is represented in the token accurately.
* Lastly we also implemented a OIDC key manager which calculates the kid for jwk's using the SHA1 digest instead of being static, or more specifically the first 7 chars. As per https://datatracker.ietf.org/doc/html/draft-ietf-jose-json-web-key#section-8.1.1 the kid should not exceed 8 chars. While it's allowed to exceed 8 chars, it must only be done so with a compelling reason, which we do not have.
2021-07-04 06:44:30 +07:00
|
|
|
userSession.SetTwoFactor(ctx.Clock.Now())
|
2019-04-25 04:52:08 +07:00
|
|
|
|
feat(oidc): add additional config options, accurate token times, and refactoring (#1991)
* This gives admins more control over their OIDC installation exposing options that had defaults before. Things like lifespans for authorize codes, access tokens, id tokens, refresh tokens, a option to enable the debug client messages, minimum parameter entropy. It also allows admins to configure the response modes.
* Additionally this records specific values about a users session indicating when they performed a specific authz factor so this is represented in the token accurately.
* Lastly we also implemented a OIDC key manager which calculates the kid for jwk's using the SHA1 digest instead of being static, or more specifically the first 7 chars. As per https://datatracker.ietf.org/doc/html/draft-ietf-jose-json-web-key#section-8.1.1 the kid should not exceed 8 chars. While it's allowed to exceed 8 chars, it must only be done so with a compelling reason, which we do not have.
2021-07-04 06:44:30 +07:00
|
|
|
err = ctx.SaveSession(userSession)
|
2019-04-25 04:52:08 +07:00
|
|
|
if err != nil {
|
2021-07-22 10:52:37 +07:00
|
|
|
handleAuthenticationUnauthorized(ctx, fmt.Errorf("Unable to update authentication level with Duo: %s", err), messageMFAValidationFailed)
|
2019-04-25 04:52:08 +07:00
|
|
|
return
|
|
|
|
}
|
|
|
|
|
2021-05-05 05:06:05 +07:00
|
|
|
if userSession.OIDCWorkflowSession != nil {
|
feat(oidc): add additional config options, accurate token times, and refactoring (#1991)
* This gives admins more control over their OIDC installation exposing options that had defaults before. Things like lifespans for authorize codes, access tokens, id tokens, refresh tokens, a option to enable the debug client messages, minimum parameter entropy. It also allows admins to configure the response modes.
* Additionally this records specific values about a users session indicating when they performed a specific authz factor so this is represented in the token accurately.
* Lastly we also implemented a OIDC key manager which calculates the kid for jwk's using the SHA1 digest instead of being static, or more specifically the first 7 chars. As per https://datatracker.ietf.org/doc/html/draft-ietf-jose-json-web-key#section-8.1.1 the kid should not exceed 8 chars. While it's allowed to exceed 8 chars, it must only be done so with a compelling reason, which we do not have.
2021-07-04 06:44:30 +07:00
|
|
|
handleOIDCWorkflowResponse(ctx)
|
2021-05-05 05:06:05 +07:00
|
|
|
} else {
|
|
|
|
Handle2FAResponse(ctx, requestBody.TargetURL)
|
|
|
|
}
|
2019-04-25 04:52:08 +07:00
|
|
|
}
|
|
|
|
}
|