I wrote a custom authenticator, but the routes seem to be getting called without authentication anyw...

# ktor

[bdawg.io]

I wrote a custom authenticator, but the routes seem to be getting called without authentication anyways. Any ideas from the routing and the authentication pipeline snippets?

Untitled.kt

[Deactivated User]

I’m afraid there is no enough context. Since the pipeline seems to be part of the class AccountSessionAuthenticationProvider that is not included, and no clue about the register method either

[bdawg.io]

io.ktor.auth.Authentication.Configuration.register(io.ktor.auth.AuthenticationProvider) is the full header for the register method

[bdawg.io]

There’s not anything special about the AccountSessionAuthenticationProvider beside it extending from io.ktor.auth.AuthenticationProvider and it having the two configuration options on it

val authenticate: suspend (SessionToken) -> Principal? = provider.authenticate
val loginRedirectProvider: (ApplicationCall.() -> Url)? = provider.loginRedirectProvider

[bdawg.io]

Here’s the full implementation if it really does help

class AccountSessionAuthenticationProvider(name: String?) : AuthenticationProvider(name) {
    internal var loginRedirectProvider: (ApplicationCall.() -> Url)? = null
        private set

    internal var authenticate: suspend (SessionToken) -> Principal? = { null }
        private set

    fun redirectToLogin(provider: ApplicationCall.() -> Url) {
        loginRedirectProvider = provider
    }

    fun validate(validate: suspend (SessionToken) -> Principal?) {
        authenticate = validate
    }
}

[bdawg.io]

my account session authentication is pretty close to the BasicAuthenticationProvider in ktor-auth, the difference being credentials are fetched from a cookie on the ApplicationCall instead of the Authorization header. https://github.com/ktorio/ktor/blob/master/ktor-features/ktor-auth/src/io/ktor/auth/BasicAuth.kt