is there a way to get the currently selected `Route` from the `ApplicationCall`?

# ktor

[zpearce]

is there a way to get the currently selected Route from the ApplicationCall?

[Deactivated User]

http://ktor.io/advanced/pipeline/route.html#route-from-call

[zpearce]

ah, RTFM 😄 thank you

[cy]

@zpearce what is your usecase? what are you trying to lookup from the currently selected route?

[zpearce]

I'm currently playing around with attaching metadata to routes indicating which jwt scopes are required to access the route. I don't have anything really working yet - still trying to wrap my head around it

[cy]

Perhaps you need to do it similar to already existing auth

[cy]

Similar to Route.authenticate()

[cy]

http://ktor.io/features/authentication.html

[zpearce]

the jwt auth implementation gives me a validate function where I can verify the jwt, but it doesn't give me the ability to assign different required scopes to routes.

[zpearce]

at first I thought I could write my own extension functions on Route (get, post, etc) that take a list of required jwt scopes. That metadata would need to be stored somewhere that is accessible in the validate function, where I could compare the scope claim of the incoming jwt against the list of required scopes for the current route

[cy]

How man "scopes" do you have? Can't you simply register multiple JWT authenitcators for every scope ?

[zpearce]

ahh, I think I see what you mean. Different named authenticators (all jwt based) that themselves keep the metadata about required scopes?

[cy]

yes, exactly

[cy]

however it wouldn't work if you have too many scopes

[zpearce]

right

[cy]

or if the list of scopes is dynamic

[zpearce]

as of now my project doesn't have that many. I'll give that a try and see how I like it. Thanks for the idea

[cy]

It looks like we need some kind markers to be passed with configurationNames that need to be available in verifiers. But this requires design, we can think about it