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.
Related
I have a working APEX installation, running ORDS in standalone mode, with several applications in use.
I have enabled my schema for ORDS and installed the sample service.
However, when I try to test the https:///ords/rest/hr/employees/ service, I get a 404.
I've tried:
Another schema within the installation, and it doesn't work there either.
Resetting the sample service. Nada.
De-registering and re-registering the schema under a different alias and installing the sample service again. Zip
Why this isn't working?
After much research and trials, I've found the answer:
TLDR: the password for the ORDS_PUBLIC_USER has expired
I found this article that talks about this problem, from which I was able to figure things out.
Apparently, by default, passwords expire after 180 days (of non-logging in?) and the corresponding account is locked. This seems to have no effect on the general operation of ORDS or APEX, since our production environment has been running without a problem for over a year.
The article recommends resetting the passwords of the following system accounts.
APEX_PUBLIC_USER
APEX_LISTENER
APEX_REST_PUBLIC_USER
ORDS_PUBLIC_USER
However, upon running
select * from dba_users where username like 'APEX%'
I could see that only the ORDS_PUBLIC_USER account was locked, so I only dealt with that one.
The article said to use the original passwords from when ORDS was installed, but upon inquiring what that was, I thought it too unsafe, so I decided to change it. That meant two things:
Resetting the users database password with
alter user ORDS_PUBLIC_USER identified by password account unlock;
( change password to your desired password )
Change the password in the corresponding password file, which can be found at a path similar to /ords19/prod/ords/conf/apex_pu.xml and looks like this.
Replace the value of the db.username entry with an exclamation mark, followed by the plaintext password of your choice, and save the file. Thus, if you wanted to use the password foobar, you'd put !foobar. (Don't worry: When ORDS restarts and reads the file, it encrypts the password and writes the encrypted version back to the file so no one snooping around in your filesystem can get at it.)
After I did all this, I restarted ORDS, and voila! My REST sample service now returns data as intended! Thank you Internet.
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.
I just noticed I cannot login in my Jenkins.
How can I reset my password and access to my account again? I do not see any link to recover passwords and they seem to be hashed in the installation directory.
In How to reset password of Jenkins you have a set of tricks to make this happen. I based my solution on it, but it diverges in a certain point.
This is what I did to solve the issue:
Let's assume Jenkins' directory is stored in $JENKINS (in my machine this is /var/lib/jenkins/) and your username is user.
Allow signups by disabling disableSignup. This means editing $JENKINS/config.xml and setting this option to false:
<disableSignup>false</disableSignup>
Restart Jenkins (service jenkins restart).
Enter in Jenkins and register a new user, for example testuser, with the password being the one you want to set to your user user.
Extract the hashed password from $JENKINS/users/testuser/config.xml. You will see something like:
<passwordHash>#jbcrypt:$2a$10$PY7p4dxFiGSgJpxiNVTQDuJKAQ8pr9snDgQXaafogjErvgB0oC3qy</passwordHash>
Set the user's password to this one in <passwordHash>. That is, edit $JENKINS/users/user/config.xml and replace the password there to set the one above.
Disallow signups back by enabling disableSignup. That is, in $JENKINS/config.xml set the disableSignup option back to true:
<disableSignup>true</disableSignup>
Restart Jenkins again.
Note you can also replace the password directly by generating a jBCrypt. For example, in http://www.mindrot.org/projects/jBCrypt/ you can find some Java code for it.
A different approach for Windows that solved this issue for me:
In
C:\Windows\System32\config\systemprofile\AppData\Local\Jenkins\.jenkins\config.xml, change useSecurity to false.
The restart Jenkins, you will now get full access without login. Go to People, select the old admin user and delete the user.
Then set
<disableSignup>false</disableSignup>
and
<useSecurity>true</useSecurity>
Restart Jenkins again, and you will now be able to register again.
Finally
<disableSignup>true</disableSignup>
We have recently created a new database instance for an upgraded application. When we try to connect to the DB using ODBC from Excel it returns a "ORA-01017: invalid username/password; logon denied" error.
I am able to successfully logon to the database with SQL+ from the command line using the same username and password.
If I switch back to the previous database I can connect successfully using Excel.
Does anyone know what if anything needs setup on the new DB to allow it to accept the ODBC connection.
Something springs to mind years back when we first set this up about either username/passwords being converted to uppercase when trying to connect so both the USERNAME and PASSWORD are set to uppercase. I'm not sure whether anything else is needed server side or not.
Any help would be greatly appreciated.
ORA-01017: invalid username/password is always because of wrong username password combination.
Quite likely that the password is not in the right case in your Excel.
For the case sensitivity, check the SEC_CASE_SENSITIVE_LOGON parameter in the DB.
If parameter is set to true, passwords are case sensitive.
The issue isn't to do anything with the database, it is the connection string I'm using to connect to the database. It's using the old instance instead of the new one!!! I need to look at why that is using the old one when tnsnames is setup to point to the new one.
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