i have this problem where the authentication routes don't need auth guard, but the config key for auth middleware is set to both routes. i use sanctum as the auth guard, so the authentication routes are inaccessible as it throws Target class [sanctum] does not exist. as the server response.
currently, both routes have the config key webauthn.guard for its middleware, with the registration having it on its auth middleware. it would be convenient for api creation if both routes can have their own guard configuration.
i have this problem where the authentication routes don't need auth guard, but the config key for auth middleware is set to both routes. i use sanctum as the auth guard, so the authentication routes are inaccessible as it throws
Target class [sanctum] does not exist.as the server response.currently, both routes have the config key
webauthn.guardfor its middleware, with the registration having it on its auth middleware. it would be convenient for api creation if both routes can have their own guard configuration.these are the code lines in question:
https://github.com/asbiin/laravel-webauthn/blob/8f16d6ba3df1d7291b83f75710af1c7bdddef326/routes/routes.php#L13
https://github.com/asbiin/laravel-webauthn/blob/8f16d6ba3df1d7291b83f75710af1c7bdddef326/routes/routes.php#L29
i haven't found other solutions than to edit the vendor files directly, as i am quite a beginner at this
many thanks in any case