Some user cant login to octopus

Legacy Authentication
,
1

Hi there,

I wonder if anyone in here have experience with when user try login to octopus , it gets bad request - request too long
HTTP error 400. the size of the requests headers is too long.

Maybe something to do with user’s token? but this is the first time he try to login

3

Hi,

Thanks for reaching out and sorry to hear you’re having difficulties. To help troubleshoot the issue you’re having could get some additional details?

Which authentication provider(s) are you using? E.g. Octopus username/password, Active Directory, Azure AD?

Is the error you are seeing appearing in the UI or in a log (or both)? Are you able to attach a screenshot to illustrate?

Regards
Shannon

4

Thanks for replay Shannon, this is fixed now. its a user error

5

We are facing the same issue for some users.we are getting this error while login to the portal.we are using active directory authentication.Facing this issue only for few users .can you please help?
Http 400 error.size of request header is too long

6

Hi @rinoshjacob,

Thanks for getting in touch!

There is some information here that may point you in the right direction: https://support.microsoft.com/en-gb/help/2020943/http-400-bad-request-request-header-too-long-response-to-http-request

If this doesn’t help then you would be best starting a new topic for this issue, as replies to old topics can get missed.

In the new topic try to include as much information as possible such as:
Octopus Server version
Where the error is appearing - screenshots if possible
Any obvious differences between the users that this works for and the ones it doesn’t, specifically within their AD configuration?

Regards,
Paul