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

Avoid entering local network credentials in Http #1435

Open
BielBabtec opened this issue Oct 8, 2024 · 4 comments
Open

Avoid entering local network credentials in Http #1435

BielBabtec opened this issue Oct 8, 2024 · 4 comments

Comments

@BielBabtec
Copy link

Which version of Duende IdentityServer are you using?
We are using the version 7.0.6

Which version of .NET are you using?
We are using the version 8.0.204

On a local network, if our clients do not have the web application configured to use https, every time they want to connect to Duende to log in, they will have to enter local credentials to allow the browser to connect to the application in a server in the local network.

We want to know if it is possible to add some configuration in duende to avoid requiring these credentials in installations that are not configured to use https on local networks.

Best regards

@RaulRG
Copy link

RaulRG commented Oct 10, 2024

Some clarification: my mate means that the users get a form from the browser to introduce their Windows' credentials. This is even before the user decided to use single sign on with Windows. It could be that they decide to use a username / password combination that we stored in our database.
We are displaying a form with fields for username / password and a button that they can press if they prefer to use single sign on with Windows. They get the form even without pressing the button. Could we do something to avoid introducing the Windows' credentials? The customers will use https anyways, but in our test environments and before configuring the certificates there is a time where the customer don't yet have https

@RolandGuijt RolandGuijt self-assigned this Oct 11, 2024
@RolandGuijt
Copy link

I suggest using https throughout. When using mixed http and https configurations subtle behavior differences are known to happen.
Also because of these differences using http on test and https elsewhere could lead to more problems.

Finding out the cause of your problem might take a lot of time that could imo be better spend on configuring https on test.

@RaulRG
Copy link

RaulRG commented Oct 11, 2024

We completely agree with you and our customers install https anyways. Our hope was that this could be something that Duende already knows and where a workaround could be available. Months ago we were using the open source IdentityServer over the http.sys implementation and we didn't have this issues (or it didn't happen so often). Now we upgraded to Duende's IdentityServer using Kestrel and the form displays every time we access it

@RolandGuijt
Copy link

Can you please show us the code where you configured Windows authentication?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

3 participants