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

System.DirectoryServices.AccountManagement - Invalid URI after upgrade to 9.0 #110400

Closed
maxima120 opened this issue Dec 4, 2024 · 2 comments
Closed

Comments

@maxima120
Copy link

maxima120 commented Dec 4, 2024

Description

I have stable WPF .NET 8 app. After upgrading System.DirectoryServices.AccountManagement from 8.0.1 to 9.0 I got this error:

System.UriFormatException: 'Invalid URI: The hostname could not be parsed.'

Reproduction Steps

var ctx = new PrincipalContext(ContextType.Domain);
var usr = UserPrincipal.FindByIdentity(ctx, IdentityType.SamAccountName, "myname");
var test = usr.GetGroups();

Expected behavior

no exception

Actual behavior

exception

Regression?

Worked for couple years now.

Known Workarounds

Downgrade to 8.0.1 solves this immediately.

Configuration

Windows 10 Enterprise with login via LDAP.

Other information

No response

@dotnet-issue-labeler dotnet-issue-labeler bot added the needs-area-label An area label is needed to ensure this gets routed to the appropriate area owners label Dec 4, 2024
@dotnet-policy-service dotnet-policy-service bot added the untriaged New issue has not been triaged by the area owner label Dec 4, 2024
@maxima120 maxima120 changed the title Invalid URI after upgrade to 9.0 System.DirectoryServices.AccountManagement - Invalid URI after upgrade to 9.0 Dec 5, 2024
@vcsjones vcsjones added area-System.DirectoryServices and removed needs-area-label An area label is needed to ensure this gets routed to the appropriate area owners labels Dec 5, 2024
Copy link
Contributor

Tagging subscribers to this area: @dotnet/area-system-directoryservices, @jay98014
See info in area-owners.md if you want to be subscribed.

@steveharter
Copy link
Member

steveharter commented Dec 5, 2024

This is a duplicate of #109858 which is fixed in v10 and being ported to 9.0.x.

@steveharter steveharter closed this as not planned Won't fix, can't repro, duplicate, stale Dec 5, 2024
@dotnet-policy-service dotnet-policy-service bot removed the untriaged New issue has not been triaged by the area owner label Dec 5, 2024
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