NuGet access policy changes from microsoft

[DGuidi]

Looks that microsoft deprecated password-based authentication for nuget.org in favor of microsoft accounts. I received a mail yesterday to migrate authentication system before September 17, when "we will expire your password to protect your account from unauthorized access".
No problem for me, but I think this can block management issues from other NTS admin.
Any suggestion?

@FObermaier @airbreather I will send you the original mail I received

[xivk]

Perhaps we can get an organization account?

https://docs.microsoft.com/en-us/nuget/nuget-org/organizations-on-nuget-org

[xivk]

Hmm nevermind, looks like it's there already... carry on!

[DGuidi]

ok, so maybe I received an alert from nuget for my personal nuget account and there's actually no problems for NetTopologySuite - Team account?
I hope so :)

[airbreather]

I think @FObermaier transformed the "NetTopologySuite - Team" user account to an "organization" (which doesn't have a real "account" anymore), which would explain some minor problems I ran into when releasing v2 thinking that the legacy full-access API key would still work.

If that's the case, then the "NetTopologySuite - Team" account doesn't "really" exist anymore; it's just an umbrella. Any of us can publish packages owned by the organization using our own logins / API keys.

Right now, for example, the .travis.yml files use this scoped API key I have on my account (the actual details of the key are in the secret spot so that you can add it to other NTS projects):

[DGuidi]

Ok so password associated to organization username (see GitHub nettopologysuite team administration area) aren't valid anymore right?