[GH-ISSUE #60] FR: add ability to use built-in authentication for custom routes #19

New issue

Closed

opened 2026-05-23 08:38:39 -06:00 by gitea-mirror · 2 comments

gitea-mirror commented

2026-05-23 08:38:39 -06:00

Owner

Originally created by @donl on GitHub (Dec 7, 2022).
Original GitHub issue: https://github.com/appy-one/acebase-server/issues/60

Looking to be able to use the built-in authentication on endpoints created by server.extend and server.app to check if a request is from an authenticated user or not.

Originally created by @donl on GitHub (Dec 7, 2022). Original GitHub issue: https://github.com/appy-one/acebase-server/issues/60 Looking to be able to use the built-in authentication on endpoints created by `server.extend` and `server.app` to check if a request is from an authenticated user or not.

gitea-mirror closed this issue

2026-05-23 08:38:40 -06:00

gitea-mirror commented

2026-05-23 08:38:43 -06:00

Author

Owner

@appy-one commented on GitHub (Dec 7, 2022):

You should be able to use req.user for this purpose. If the user is signed in, it will contain the user details, null otherwise.

@appy-one commented on GitHub (Dec 7, 2022): You should be able to use `req.user` for this purpose. If the user is signed in, it will contain the user details, `null` otherwise.

gitea-mirror commented

2026-05-23 08:38:43 -06:00

Author

Owner

@donl commented on GitHub (Dec 7, 2022):

Ahh! That looks perfect! Thanks

@donl commented on GitHub (Dec 7, 2022): Ahh! That looks perfect! Thanks