I have username admin. But now I forget my password.I want to reset my password in blue prism. How to recover my password?
This isn't the official script distributed by Blue Prism (as #Jerry pointed out the existence of), but one I've used against several installations to force a reset of the password.
Blue Prism v6
This finds the user with the username admin and resets their password back to the original admin string. It will force a password change for admin on their next logon.
USE blueprism
UPDATE BPAPassword SET salt = '', hash = '208512264222772174181102151942010236531331277169151', type = 0
WHERE userid = (SELECT userid FROM BPAUser WHERE username = 'admin')
Blue Prism v5
This script will change every user in the environment's password back to admin, but will not force a password change on the next log in. There is likely a more elegant way to do this and target just the admin user, but unfortunately I no longer have access to a v5 schema to test this on.
USE blueprism
UPDATE BPAUser
SET password = '208512264222772174181102151942010236531331277169151'
As an alternative to the script solution, you can also manually update the BPAPassword table using SQL Server Object Explorer (built-in in Visual Studio) to reset password to admin as follows:
find the desired user in the BPAUser table and copy userid
find the row with same userid inside BPAPassword table
update following columns
type -> 0
salt -> ''
hash -> 208512264222772174181102151942010236531331277169151
You can reset the password by running a query in the MS SQL Database in which BluePrism stores everything it uses. As for what query that is, it looks like it depends on the version of BluePrism, per this page:
How can I reset my Blue Prism admin password?
If you forget your Blue Prism admin password and/or exceed the maximum number of allowed login attempts, then please contact support#blueprism.com for details on how to request the relevant admin password reset scripts.
We have several scripts which you can use to reset the password for the 'Admin' account. The script command is specific to the version of Blue Prism you are using.
Important: These scripts should only be run by a Database Administrator or someone who has an understanding of SQL.
If it is an enterprise level then, you need to raise ticket to IT team. They will reset the password and inform you.
If Blue Prism is installed on local machine with local database credentials then there is an trick to reset it.
Irrespective of the version, you can follow the same steps. As I have version 6. below screen shots are with respect to version 6. But the fundamental tasks will be the same.
Steps are as below:
As we know While installing Blue Prism on the system, It will ask for the connection. Considering the "Default connection" password needs to be reset. Follow the following steps:
Click on Blue Prism icon
Click on Configure link on login window below window will appear
Click on New Connection button. Following window will appear with default connection name. In my case it is connection2
As this steps need to be carried out on local machine, use the local database instance name as Database server and give name Database Name
Fill the required details, and click on Create Database. Once the Database created successfully, just ensure once again click on Test Connection and validate the connection establishment between Blue Prism and SQL Server
Note: In the SQL Database, database will be created with the name given in Database Name field
Open SQL Server Instance, you'll be finding the Database Name (value mentioned in field)created.
Navigate to Database Name --> Tables--> BPAPassword and hit the following query
Select * from BPAPassword. In the output table, salt and hash the main two column for which we are looking for.
Note: We're doing this, as we know when we install Blue Prism and try for login the initial username and password will be admin. As soon as, we login with the default credential it will ask for change password.
Blue prism will store all the values in encrypted mode in Database, So decryption of the values will be impossible as human.
As this is a new connection for Blue Prism, for this connection default password will be admin
Now, Copy the value of salt and hash.
Connect the database which is used for Default connection. And update the salt and hash column in BPAPAassword Table using the SQL Update statement for specific user.
Note: If you've multiple users then, goto BPAUser and find the user for which you need to reset the password.
NOTE: This will be carried out only on local machine. If it happened within organization please connect to IT team to password reset. Please do not create the database on the organization database server as it may affect the Blue Prism server which is configured already as per organization requirement
You can just enter admin as user and admin as password. Thereafter you are redirected to a window that will allow you to enter a new password.
Related
I have a script from BluePrism to reset my "admin" password. It is the Learning edition 6.9.0.
What I can't figure out is how to actually apply that script to the BluePrism database.
I have MySql installed on my PC and I was hoping I could that to run the scripts, but I can't find an option to connect MySql to the blueprism database.
I can find the BluePrism database no problem, but MySql won't recognise it as a database file.
I have also tried setting up a new connection inside BluePrism itself but to no avail.
Thanks in advance for any assistance.
Here is a Solution that works for me.
This isn't the official script distributed by Blue Prism (as #Jerry
pointed out the existence of), but one I've used against several
installations to force a reset of the password.
Blue Prism v6 This finds the user with the username admin and resets
their password back to the original admin string. It will force a
password change for admin on their next login.
USE blueprism
UPDATE BPAPassword SET salt = '', hash = '208512264222772174181102151942010236531331277169151', type = 0
WHERE userid = (SELECT userid FROM BPAUser WHERE username = 'admin')
Also here is a video with another process that changes it to another password, maybe you could try it, if the first solution does not work or if you like a more visual resource.
How can I reset the admin password in Datastax Opscenter? Will disabling and reenabling authentication in /etc/opscenter/opscenterd.conf do the trick? Will I lose any other data in the process?
I'm not aware of an official way to simply reset the admin password in OpsCenter. However, I do know of a "hacky" way to do it, if you're up for that (and if you have physical or ssh access to the server).
OpsCenter's user authentication is maintained in a SQLite database file named passwd.db, located in the root of your OpsCenter directory. The file is created once you enable user authentication in OpsCenter. Using sqlite3, you can open and manage this file:
$ sqlite3 passwd.db
SQLite version 3.8.5 2014-08-15 22:37:57
Enter ".help" for usage hints.
sqlite> PRAGMA table_info(users);
0|id|INTEGER|0||1
1|username|TEXT|0||0
2|password|TEXT|0||0
3|groupid|INTEGER|0||0
sqlite> SELECT * FROM users;
1|admin|8c6976e5b5410415bde908bd4dee15dfb167a9c873fc4bb8a81f6f2ab448a918|1
Looking above, you can see the row for the "admin" user of a brand new install of OpsCenter 5.2.1 is the hash of:
8c6976e5b5410415bde908bd4dee15dfb167a9c873fc4bb8a81f6f2ab448a918
If you update the password field on the users table to that value, it should reset it back to the original:
UPDATE users
SET password='8c6976e5b5410415bde908bd4dee15dfb167a9c873fc4bb8a81f6f2ab448a918'
WHERE username='admin';
I don't know if the passwords on different versions of OpsCenter use the same hash or not, but this should work if you're using OpsCenter 5.2.1. Otherwise, if you have a user in there that you do know the password to, you can (look up and) set the admin password to that hash, and then at least you'll know the password and be able to log in.
Turns out this was fairly simple. All I needed to do was stop OpsCenter, rename (or remove) passwd.db, and restart OpsCenter again. The daemon automatically creates a new password db file and sets the admin password to 'admin'.
I'm currently building an application that has to conform with SOX auditing requirements. One of these, is that all inserts, updates and deletes (but delete you can ignore), need to leave a trail that is difficult, if not impossible for a standard user (or non-DBA) to change.
This means, I need to enforce the auditing at the database level via triggers on insert, update and delete.
My problem is; this is a webapp... The typical design pattern is to store users as "logical", for example; in a "users" table. What I need, is for the application to actually run as the logged in user after the initial login.
My thinking (which is likely not the best) is to do the following:
Load the login page via a standard username (webapp)
Check a table called "stored_users" for their logical username/password.
If they enter the correct user/pass; retrieve the db username, generate a session password (stored in KVSession on redis), update the user on the postgres DB and login with it.
After a defined time of inactivity, destroy the password session, reset the db password for the user and log them out.
Does this sound like a safe way to ensure the following?
My users are always using postgres users; so I can enforce the triggers via CURRENT_USER etc..
Security by always regenerating the postgres user password with a random, temporary password
I'd really like to hear what others have to say on this matter; as I really can't find this on Google (or I'm not searching the right terms). It seems the prevailing mindset for user logins is to store them as logical records and have a global connection user.
To achieve your goal
all inserts, updates and deletes, need to leave a trail that is
difficult, if not impossible for a standard user to change.
you can create:
1) Two schemas: one for common tables, one for security stuff like login/pass(hash) table, user session log, change log table, etc.
2) Two users: one common user, that can only use dml on common schema (no ddl), one superuser.
3) Login function that will check provided user/pass against login/pass table and log successful/failed attempts into user session log (you need SECURITY DEFINER function)
4) Set of audit triggers on common schema tables that will check the user privileges and log any changes, made by the user (SECURITY DEFINER functions here too).
I am trying to create a application using innoscript. I need to create/edit registry information values in HKLM. Hence I need admin privileges to install the application.
However, if a non admin user try to install the application, innoscript require admin user password, once they enter the admin user password, whenever I query the registry in installation script (say, HKCU), it retrieves information from the admin user. But I would like to get information from the currently logged in user. As a result, program installed under the admin user location instead of current logon user account.
Is there a way to get current logon user user and user app data location from innoscript, when the application is started with Run as administrator or prompted admin user.
Awaiting your update.
Thanks,
The installer is not supposed to read or modify any per-user state (including HKCU) during a per-machine installation (and there is no way to do so reliably). You should instead make the application itself do this on first run (by trying to read the appropriate location and assuming default values if they were not found).
Remember, an application is installed once, but can then be run by several different users. This behaviour is essential.
An easy workaround is to move your logic to an executable instead of Pascal script. Then you can call this executable in [Run] section,
http://www.jrsoftware.org/ishelp/index.php?topic=runsection
Remember to mark the Run item as runasoriginaluser.
I have a website that uses Windows Authentication to authenticate its users. Normally when a user accesses the site on an IE browser the username field is populated with the computers domain name and user name. This is usually incorrect and the user enters the correct username and their password and can access the site.
I have a user now on Windows 7 IE8(I beleive) and the username field in the credential prompt is being autopopulated with domain\userName except the username is incorrect and we cannot change it. The user is unable to log into the site because of this. Has anyone experienced this before? Does anyone know why the username field cannot be changed? Solutions I have tried:
Clearing cache and stored form data/passwords etc
Site is in users trusted sites. So I had the user change the settings to "Prompt for username and password" but the prompt still comes up with the username autopopulated and does not let her change it.
I have never run into this before. Our users do not have any issue logging in, its just this one corporate location that was just set up and is running Windows 7(Rest of the company is under Windows XP) If it matters this is a sharepoint 2010 web application
Any help on this would be greatly appreciated as I have an entire group of users with this problem. Im willing to bet this would not be an issue in a different browser but they need to be able to use IE for application compatibility reasons.
Thanks!
I was able to fix it by doing the following:
Go to Start, Control Panel, User Accounts, then click Manage Your Credentials, and look for the credentials to your site, if they are there Modify and “Remove from vault” ( I suppose you could Edit them to the correct credentials but I just removed it and it did not prompt her).
She had the wrong credentials stored there. Im not sure why clearing the cache and passwords from the internet options didnt work but this did.
I had this problem with a user where the domain stored with the credentials could not be changed. This is the only item online I could find even close to my problem. The user saw "user-pcdomain\localusername" auto entered in the form. He tried to correct it with "workdomain\workusername" but got a message saying "Please enter a user name and password". Eventually we realized that his system was sending "user-pcdomain\workdomain" as his username. I've never seen a login misfire like that.
In his case he did not have his credentials stored but needed to add credentials - "workdomain\workusername" - for all of the domains he needed to access.
The point is - to expand on the answer - that IE or Windows 7 or both will store credentials incorrectly on rare occasions and the solution is be creative about adding\editing\remove credentials with Manage Your Credentials