Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

HTTP Authentication doesn't work for Kerberos #1309

Closed
AlexanderMoskovkin opened this issue Mar 14, 2017 · 4 comments
Closed

HTTP Authentication doesn't work for Kerberos #1309

AlexanderMoskovkin opened this issue Mar 14, 2017 · 4 comments
Assignees
Labels
STATE: Auto-locked An issue has been automatically locked by the Lock bot. TYPE: bug The described behavior is considered as wrong (bug).

Comments

@AlexanderMoskovkin
Copy link
Contributor

Created from the discussion.

@thecodejack:
Just to add more, we follow kerberos authentication. Most of applications don't even have login pages. So need a way to apply custom headers.

@inikulin:
Have you tried HTTP auth feature? It supports NTLM authentication with which Kerberos is back compatible

@thecodejack:
Reg NTLM. Yes. I have NTLM. But no luck. it is logging out.

@AlexanderMoskovkin AlexanderMoskovkin added the TYPE: bug The described behavior is considered as wrong (bug). label Mar 14, 2017
@inikulin inikulin added this to the Sprint #6 milestone Mar 21, 2017
@inikulin inikulin modified the milestones: Sprint #7, Sprint #6 Apr 24, 2017
@AlexanderMoskovkin AlexanderMoskovkin modified the milestones: Sprint #7, Planned May 26, 2017
@zhaighin
Copy link

Can this bug be fixed asap? I have been waiting the fix since the ticket created.

@churkin
Copy link
Contributor

churkin commented May 29, 2017

Hi @zhaighin, Unfortunately it is very difficult to implement Kerberos authentication in the testcafe. It has a very complex mechanism to generate authentication tokens and at the moment there is no complete universal nodejs module for this. All we can do is add the ability to set Authentication header value that you will need to generate yourself. For this we have created #1306 issue. At the moment we can't suggest you another solution.

@AlexanderMoskovkin AlexanderMoskovkin removed this from the Planned milestone Aug 2, 2017
@AlexanderMoskovkin
Copy link
Contributor Author

According to the last comment I close it as a duplicate for #1341

@lock
Copy link

lock bot commented Mar 28, 2019

This thread has been automatically locked since it is closed and there has not been any recent activity. Please open a new issue for related bugs or feature requests. We recommend you ask TestCafe API, usage and configuration inquiries on StackOverflow.

@lock lock bot added the STATE: Auto-locked An issue has been automatically locked by the Lock bot. label Mar 28, 2019
@lock lock bot locked as resolved and limited conversation to collaborators Mar 28, 2019
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
STATE: Auto-locked An issue has been automatically locked by the Lock bot. TYPE: bug The described behavior is considered as wrong (bug).
Projects
None yet
Development

No branches or pull requests

5 participants