Home/ Questions/Q 7771859
In Process

The Archive Base Latest Questions

Editorial Team
  • 0
Asked: 2026-06-01T16:45:07+00:00

I have some code in a EF Code First initializer that is grabbing the

  • 0

I have some code in a EF Code First initializer that is grabbing the Membership Provider (ASP Universal Provider) and seeding some users. I know that isn’t necessarily normal scenario but it has been working great in local dev. When pushing to Azure I sometimes see it not work. I see the records created in the Membership tables created, but when I log in with the password it doesn’t match. Updating the salt and password with values from my local also don’t seem to work. Is there something specific about the machine or OS for the salt/password generation or validation? It doesn’t make sense because that would mess up any farm scenario, just looking for any help on why I might see something like this.

Share

Leave an answer

You must login to add an answer.

Need An Account,

1 Answer

  1. Editorial Team

    Yes, if you set the machine key explicitly, Membership Provider uses that key to encrypt the password.

    So you need to have same machine key in all web.config files.

    • 0