# How to send token authentication to backend using okta and standalone Angular and SpringBoot 3 login widget **URL:** \ **Category:** OAuth/OIDC\ **Tags:** spring, angular\ **Created:** [May 7, 2024, 11:05am UTC](https://devforum.okta.com/t/how-to-send-token-authentication-to-backend-using-okta-and-standalone-angular-and-springboot-3-login-widget/28121 "2024-05-07T11:05:53Z")\ **Posts on this page:** 1\ **Showing post:** 3
**Author:** ![daniel.sanders](https://avatars.discourse-cdn.com/v4/letter/d/8dc957/32.png) [@daniel.sanders](https://devforum.okta.com/u/daniel.sanders)\ **Post date:** [May 24, 2024, 3:44pm UTC](https://devforum.okta.com/t/how-to-send-token-authentication-to-backend-using-okta-and-standalone-angular-and-springboot-3-login-widget/28121/3 "2024-05-24T15:44:48Z")
Hello @shirukento1, You might check some of the solutions over in this thread: [Getting 401 error while calling spring-boot api from angular app - #17 by mraible](https://devforum.okta.com/t/getting-401-error-while-calling-spring-boot-api-from-angular-app/14371/17) Essentially, I’d make sure that the callback route is correctly configured, and if you are passing through OktaAuthGuard you can check for errors there: [GitHub - okta/okta-angular: Angular SDK for Okta's OIDC flow](https://github.com/okta/okta-angular?tab=readme-ov-file#oktaauthguard) - this could be something you need to use to access a protected route using the ID Token, so if you aren’t using this it may be a good idea. In the case of the above post it was removed to resolve the situation, which indicates it’s not a protected route using that function and possibly that the ID Token check is coming from somewhere else. --- _[View the full topic](https://devforum.okta.com/t/how-to-send-token-authentication-to-backend-using-okta-and-standalone-angular-and-springboot-3-login-widget/28121)._