I forgot my Orchard admin password, so I googled around on how to (manually) reset it. I found this article on how to achieve this.
So I went to my server, opened the website in WebMatrix, opened the database, set a new password and the PasswordFormat to Clear. I opened the site and tried to login, but still it said that the UserName and/or password was incorrect.
Has anyone ever got a similar issue? Any thoughts on why it doesn't work?
I am using Orchard 1.8 and WebMatrix 3.
Thanks
Okay I found the solution. If anyone else runs into this issue here is wat was the problem:
In Orchard 1.8 information is also stored as XML in the table Orchard_Framework_ContentItemRecord. By editing the rows ALSO in here, the effects take place and the password can be reset!
I had access to another user and access to the database which I edited and replaced the admin user's hash and salt with the user I knew the password to , could then log in with that password.
Related
I just created a thread in the Liferay forum about my problem, I would appreciate it if you answered here and if possible also there.
I am working with Liferay 6.2.5 CE and this is what I am trying to achieve:
Integrate CAS for SSO
On successful create a Liferay User and
Redirect to default private page or to the requested url
On logout delete the user
Important: Liferay is not going to use any LDAP.
I am stuck in the step two, I am not clear what I need to program or to configure. I found this article that seems to do what I need but it is from 2013 and maybe there is a better way to do it (not modifying directly the server files)
Thank you.
I've had to modify CASFilter too in Liferay 6.2 and I think your only option is to modify server files like the tutorial says. It is not that hard
I have tried a lot of settings, WebMatrix vs Build from source code, sql vs sql compact version. Different version of Orchard.
But they all have the same problem: Fail to login
When you accesss
http://localhost:43327/admin
Even password/username view cannot be loaded.
Address bar is showing:
http://localhost:43327/Users/Account/LogOn?ReturnUrl=%2F
How to solve this problem?
Check if the user specified in the connection string does has the access to the database.
Are you using a connectionstring with UserId and Password or using Integrated Security?
I changed the theme, #Model.Content was not there.
Not view for Login will show up..
I'm trying to go to the references on an Access Database. I'm not very familiar with this database but here's my history with it:
I tried to open the code files once and it asked for a password
Prior developer assured me there was no password on it and he was able to get into the code files just fine.
I then tried and, to my surprise, it no longer asked me for a password
Today I try to get into Tools/References and the password box is back.
Allegedly this mdb is not supposed to be protected. Any help if figuring out how to get past this would be greatly appreciated!
The original programmer removed the password that was required to get into the code, but then we found there was another level of security protecting the project references. The original programmer couldn't figure out how to remove that password, but he was instead able to change it to something that wasn't personal.
So I never really got the answer I was looking for but I think the moral of the story is that people need to not use personal passwords for their work stuff so that when I take over their work they can just tell me what it is instead of making me wait a month for them to come back and change it.
I've got a SharePoint MOSS 2007 development setup on to which I installed the WSS infrastructure update. Now, whenever I try to access any site collection in my SharePoint farm using IE7 I get a username and password prompt. I enter valid credentials for my Site Collection admin account and I see the box again. This happens three times then after the third time I just see a blank page.
When I access the system through FireFox 3.0 I get the username and password screen but after putting the credentials in the first time, the site runs as normal.
I presume this is because IE is using NTLM whereas Firefox is using basic authentication, but I'm not sure how to resolve the issue.
Has anyone else experienced this or can anyone point me in the right direction?
Thanks in advance
- Russell
I've found the answer to this now. It was all to do with this issue...
http://support.microsoft.com/kb/896861
Before the infrastructure update just entering the FQDN (e.g. intranet.domain.local) for BackConnectionHostNames entry in Method one worked fine. After the infrastructure update I added just the hostname (e.g. intranet) to the BackConnectionHostNames entry and this fixed the issue! :-)
I had to turn off IE ESC to get this to stop. For some reason, it worked on all servers except one in our farm. Who knows. Hope this helps you get started.
The bossman wants to know how to delete a user in Sharepoint. We've got him convinced that deleting a user is too difficult because of traces of that user through the system, so now he wants to be able to change the username to all Xs or somesuch. I've poked around the DB and found a couple of UserInfo tables, one in SharePoint_AdminContent_<guid> db and another in SharedServices. Is there a better way to change usernames? Am I on the wrong track?
Thanks.
There is "stsadm -o deleteuser". See this TechNet article. That command will delete a user from a site collection.
You can also find more options on Keith Richie's blog. That is from WSS 2.0 / SPS 2003 era but there is a lot of good information there.
Please don't access the database directly as it's not supported ; you may even destroy integrity in the process.
If you really want to "remove" all trace of a user, I suggest looking to "stsadm -o migrateuser" to rename the user to a dummy XXX user created in your membership provider.
Edit: it's migrateuser and not renameuser, my mistake
http://technet.microsoft.com/en-us/library/cc262141.aspx
The reason you cannot remove users from SharePoint is because users are not stored in SharePoint. Users are stored in the respective membership provider: AD, aspnetsqlmembershipprovider, etc.
The process for removing a user from SharePoint's environment is to first go to your membership provider and delete the user there. After you have done this, you have a choice.
You can leave the user's artifacts for legacy information. Ie, Joe Blow created a document and even though Joe Blow doesn't exist anymore (hit by bus) it's good to know that he created the document.
Alternatively, you can run the stsadm -o deleteuser command Alex mentioned (once per site collection), which should disassociate that user from all their artifacts for that site collection. Any documents the user created will now be owned by the system administrator (I believe). An example of using this option is when the user account was misspelled and you want to remove all traces before creating the correct account.