It’s true that the default SQL Membership Provider does not allow username changes. However, there’s no intrinsic reason to prevent users from changing their usernames if you have a valid argument, on your site, to allow it. None of the tables in the SQL database have the username as a key, everything is based on … Read more
The first is the simpliest approach. Add the GUID of the user as a foreignkey in the related tables (f.e. Ordered_by). I don’t see where it breaks separating concerns. If you want to keep the order-record in database, you also have to keep the user who has ordered, that makes perfectly sense. I have used … Read more
Just for closure sake I will answer how I did achieved the goal of what my original question meant to ask for. I had two asp.net applications on one IIS server. It was my goal to make it so when user logged onto app1 their user credentials would be available in app2. Configuring the asp.net … Read more
A network-related or instance-specific error occurred while establishing a connection to SQL Server. The server was not found or was not accessible. text Generally issues like this are related to any of the following need to be looked at: firewall settings from the web server to the database server connection string errors enable the appropriate … Read more
It seems you cannot get it from the User object but you can get it this way: Guid userGuid = (Guid)Membership.GetUser().ProviderUserKey;
The semantics of ‘contains’ is not straightforward at all. In general, it would be better to use ‘index’ to test if an array has a specific value, e.g. .fruit | index( “orange” ) However, if the item of interest is itself an array, the general form: ARRAY | index( [ITEM] ) should be used, e.g.: … Read more
You are running into comparison operator chaining; 1 in () == False does not mean (1 in ()) == False. Rather, comparisons are chained and the expression really means: (1 in ()) and (() == False) Because (1 in ()) is already false, the second half of the chained expression is ignored altogether (since False … Read more
EDIT: Do not use the Membership Provider as-is because it is horridly inadequate in terms of protecting user’s passwords In light of the fact that googling “membership provider hashing algorithm” turns up this answer as the first result, and the gospel that will be inferred, it behoves me to warn folks about using the Membership … Read more
The bug is probably somewhere else in your code, because it should work fine: >>> 3 not in [2, 3, 4] False >>> 3 not in [4, 5, 6] True Or with tuples: >>> (2, 3) not in [(2, 3), (5, 6), (9, 1)] False >>> (2, 3) not in [(2, 7), (7, 3), “hi”] … Read more
Often developers struggle with the verification of a login password, because they are not sure how to handle the stored password hash. They know that the password should be hashed with an appropriate function like password_hash(), and store them in a varchar(255) field: // Hash a new password for storing in the database. // The … Read more