Skip to main content
Solved

401 (Unauthorized) - GET $eager=profile_picture

  • July 15, 2022
  • 1 reply
  • 68 views
Dennis van Leeuwen
Hero
Forum|alt.badge.img+12

When opening the Universal GUI login page, DevTools gives a 401 (Unauthorised) error. After logging in with a user with a picture uploaded in IAM the error is shown again. 
 

GET https://office.niverplast.com/indicium/iam/iam/i_ui_usr?$eager=profile_picture
401 (Unauthorized)
  • 401 - unauthorized. The user is not logged in to Indicium (anymore). Note that the login page will execute i_ui_user before login to validate whether the user has logged in or not. This may cause a 401 error on purpose if not.
Once logged in, the profile picture is displayed correctly.

Isn't this GET request an attempt to read the IAM profile picture? Isn't it unnecessary that the request is fired at the login screen? 

Best answer by Mark Jongeling

Hi Dennis,

I've checked with the team and this is intended behavior of the Universal GUI. 

This is the request to check if you are signed in or not. During the log-in process, it will perform an extra check to see if you didn't sign-in in the meanwhile. So no need to worry ðŸ˜„

 

View original
Did this topic help you find an answer to your question?
This topic has been closed for comments

1 reply

Mark Jongeling
Administrator
Forum|alt.badge.img+23
  • Mark Jongeling
  • Administrator
  • 3940 replies
  • Answer
  • August 8, 2022

Hi Dennis,

I've checked with the team and this is intended behavior of the Universal GUI. 

This is the request to check if you are signed in or not. During the log-in process, it will perform an extra check to see if you didn't sign-in in the meanwhile. So no need to worry ðŸ˜„

 

"Wake me up before you low-code"
Terms & ConditionsCookie settings

Cookie policy

We use cookies to enhance and personalize your experience. If you accept you agree to our full cookie policy. Learn more about our cookies.

 
Cookie settings