Posted on 14/12/2016 12:28:20
What? Me not understand Danglish :-).
Lets say you create a page called /profile - and that page shows the users profile. If the user is logged in, they will of course see their profile on that page and it would be different for each user eventhough the url is the same.
If that is the page you want to be called just /{name-of-user} that is a problem. You can however do that if it is ok that it is called /profile/{name-of-user}.
Since it would be the page /profile the /{name-of-user} does not have an impact on what happens on the page, except of being in the URL.
/profile is rewritten to /Default.aspx?ID=123 - /profile/{name-of-user} should then link to /Default.aspx?ID=123&userid=456.
To do that, you can create a UrlProvider. Those are pretty simple to do. See dump#1 and the example in UserUrlProvider.zip
With that you will have the profile on the /profile/{name-of-user} url if the user logs in or have autlogin.
To login the user on that page automatically based on the AccessUserID (which you now have in the URL because of the UserUrlProvider), you can write a piece of code that does that for you. An example attached in PageLoadedObserver.zip that does that. One catch is though, that it will not work if you are not storing passwords in clear text in database...
There is no publically available authentication methods that can login users without their password... For security reasons.