You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Current behavior:
Using NbPasswordAuthStrategy and the accompanying NbAuthSimpleInterceptor, the received token is inserted as HTTP header like so: Authorization: 3b023126-a007-422e-9838-839871aae08b
Expected behavior:
I would need it to be: Authorization: Bearer 3b023126-a007-422e-9838-839871aae08b
Steps to reproduce:
I generally followed the tutorial for NbPasswordAuthStrategy in the Nebular vnext Docs
Related code:
As a workaround I managed to configure a custom getter, like so:
There is a (quite dated) Stackoverflow issue describing a similar issue with NbAuthJWTInterceptor, where the Bearer prefix is added in a hardcoded way instead. I guess it would be useful to generally make this prefix configurable (with sensible default that won't break existing apps).
Issue type
I'm submitting a ... (check one with "x")
Issue description
Current behavior:
Using
NbPasswordAuthStrategy
and the accompanyingNbAuthSimpleInterceptor
, the received token is inserted as HTTP header like so:Authorization: 3b023126-a007-422e-9838-839871aae08b
Expected behavior:
I would need it to be:
Authorization: Bearer 3b023126-a007-422e-9838-839871aae08b
Steps to reproduce:
I generally followed the tutorial for
NbPasswordAuthStrategy
in the Nebular vnext DocsRelated code:
As a workaround I managed to configure a custom getter, like so:
Other information:
There is a (quite dated) Stackoverflow issue describing a similar issue with
NbAuthJWTInterceptor
, where theBearer
prefix is added in a hardcoded way instead. I guess it would be useful to generally make this prefix configurable (with sensible default that won't break existing apps).npm, node, OS, Browser
Angular, Nebular
The text was updated successfully, but these errors were encountered: