Password Encryption and buildforge.conf

How should the db_password line look when using password encryption versus encoding? The help center says I should run <bfinstall>/Platform/bfpwencrypt -e password to get the encrypted password. But, encrypted passwords are of the form {bfcrypt:alias}encrypted password, and if I attempt that I get the following errors in <bfinstall>/log.

Starting Build Forge Management Console

openssl_aes_cbc_decrypt: data_len % aes->block_size != 0: 7 at /PerlApp/BuildForge/Utilities/BfCrypt.pm line 172.

Use of uninitialized value in length at /PerlApp/BuildForge/Utilities/BfCrypt.pm line 175.

openssl_aes_cbc_decrypt: data_len % aes->block_size != 0: 7 at /PerlApp/BuildForge/Utilities/BfCrypt.pm line 172.

Use of uninitialized value in length at /PerlApp/BuildForge/Utilities/BfCrypt.pm line 175.

DBI connect('DATABASE=*****; HOSTNAME=*******; PORT=*****; PROTOCOL=TCPIP','*****',...) failed: [IBM][CLI Driver] SQL30082N  Securit

y processing failed with reason "24" ("USERNAME AND/OR PASSWORD INVALID").  SQLSTATE=08001

 at /PerlApp/BuildForge/DB/Handle.pm line 110

Premature exit -- status=2

I can put the output from the bfpwencrypt command in with the bfcrypt, but that is supposed to be the format for the encoded, not encrypted, password?

Any thoughts???

Thanks!

Derek,

You need to include the entire encrypted password which is start with something like {bfcrypt:...} because that entire value needs to be provided as it contains crucial information.

Regardless if you are using password encoding or password encryption, they will start with the {bfcrypt:}.

How should the db_password line look when using password encryption versus encoding? The help center says I should run <bfinstall>/Platform/bfpwencrypt -e password to get the encrypted password. But, encrypted passwords are of the form {bfcrypt:alias}encrypted password, and if I attempt that I get the following errors in <bfinstall>/log.

Starting Build Forge Management Console

openssl_aes_cbc_decrypt: data_len % aes->block_size != 0: 7 at /PerlApp/BuildForge/Utilities/BfCrypt.pm line 172.

Use of uninitialized value in length at /PerlApp/BuildForge/Utilities/BfCrypt.pm line 175.

openssl_aes_cbc_decrypt: data_len % aes->block_size != 0: 7 at /PerlApp/BuildForge/Utilities/BfCrypt.pm line 172.

Use of uninitialized value in length at /PerlApp/BuildForge/Utilities/BfCrypt.pm line 175.

DBI connect('DATABASE=*****; HOSTNAME=*******; PORT=*****; PROTOCOL=TCPIP','*****',...) failed: [IBM][CLI Driver] SQL30082N  Securit

y processing failed with reason "24" ("USERNAME AND/OR PASSWORD INVALID").  SQLSTATE=08001

 at /PerlApp/BuildForge/DB/Handle.pm line 110

Premature exit -- status=2

I can put the output from the bfpwencrypt command in with the bfcrypt, but that is supposed to be the format for the encoded, not encrypted, password?

Any thoughts???

Thanks!

Derek,

You need to include the entire encrypted password which is start with something like {bfcrypt:...} because that entire value needs to be provided as it contains crucial information.

Regardless if you are using password encoding or password encryption, they will start with the {bfcrypt:}.

I thought so... I guess my question now becomes what command do I need to run to create the encrypted version of the password. The help center says to run '<bfinstall>/Platform/bfpwencrypt -e password', but the output of that only works when I put it in buildforge.conf as an encoded password - when I put it in buildforge.conf as encrypted - with {bfcrypt:alias} I get the errors listed in my first post?

How should the db_password line look when using password encryption versus encoding? The help center says I should run <bfinstall>/Platform/bfpwencrypt -e password to get the encrypted password. But, encrypted passwords are of the form {bfcrypt:alias}encrypted password, and if I attempt that I get the following errors in <bfinstall>/log.

Starting Build Forge Management Console

openssl_aes_cbc_decrypt: data_len % aes->block_size != 0: 7 at /PerlApp/BuildForge/Utilities/BfCrypt.pm line 172.

Use of uninitialized value in length at /PerlApp/BuildForge/Utilities/BfCrypt.pm line 175.

openssl_aes_cbc_decrypt: data_len % aes->block_size != 0: 7 at /PerlApp/BuildForge/Utilities/BfCrypt.pm line 172.

Use of uninitialized value in length at /PerlApp/BuildForge/Utilities/BfCrypt.pm line 175.

DBI connect('DATABASE=*****; HOSTNAME=*******; PORT=*****; PROTOCOL=TCPIP','*****',...) failed: [IBM][CLI Driver] SQL30082N  Securit

y processing failed with reason "24" ("USERNAME AND/OR PASSWORD INVALID").  SQLSTATE=08001

 at /PerlApp/BuildForge/DB/Handle.pm line 110

Premature exit -- status=2

I can put the output from the bfpwencrypt command in with the bfcrypt, but that is supposed to be the format for the encoded, not encrypted, password?

Any thoughts???

Thanks!

Derek,

You need to include the entire encrypted password which is start with something like {bfcrypt:...} because that entire value needs to be provided as it contains crucial information.

Regardless if you are using password encoding or password encryption, they will start with the {bfcrypt:}.

I thought so... I guess my question now becomes what command do I need to run to create the encrypted version of the password. The help center says to run '<bfinstall>/Platform/bfpwencrypt -e password', but the output of that only works when I put it in buildforge.conf as an encoded password - when I put it in buildforge.conf as encrypted - with {bfcrypt:alias} I get the errors listed in my first post?

I'm going to have to suggest that you open a PMR for this one and let the support organization dig through the configuration setup to see what is going on.

In order to get bfpwencrypt to work correctly I had to set the LIBPATH to point to <bfinstall>/openssl and then run the bfpwencrypt from within the Platform directory. That is the only way it would spit out the encrypted password.

How should the db_password line look when using password encryption versus encoding? The help center says I should run <bfinstall>/Platform/bfpwencrypt -e password to get the encrypted password. But, encrypted passwords are of the form {bfcrypt:alias}encrypted password, and if I attempt that I get the following errors in <bfinstall>/log.

Starting Build Forge Management Console

openssl_aes_cbc_decrypt: data_len % aes->block_size != 0: 7 at /PerlApp/BuildForge/Utilities/BfCrypt.pm line 172.

Use of uninitialized value in length at /PerlApp/BuildForge/Utilities/BfCrypt.pm line 175.

openssl_aes_cbc_decrypt: data_len % aes->block_size != 0: 7 at /PerlApp/BuildForge/Utilities/BfCrypt.pm line 172.

Use of uninitialized value in length at /PerlApp/BuildForge/Utilities/BfCrypt.pm line 175.

DBI connect('DATABASE=*****; HOSTNAME=*******; PORT=*****; PROTOCOL=TCPIP','*****',...) failed: [IBM][CLI Driver] SQL30082N  Securit

y processing failed with reason "24" ("USERNAME AND/OR PASSWORD INVALID").  SQLSTATE=08001

 at /PerlApp/BuildForge/DB/Handle.pm line 110

Premature exit -- status=2

I can put the output from the bfpwencrypt command in with the bfcrypt, but that is supposed to be the format for the encoded, not encrypted, password?

Any thoughts???

Thanks!

Derek,

You need to include the entire encrypted password which is start with something like {bfcrypt:...} because that entire value needs to be provided as it contains crucial information.

Regardless if you are using password encoding or password encryption, they will start with the {bfcrypt:}.

I thought so... I guess my question now becomes what command do I need to run to create the encrypted version of the password. The help center says to run '<bfinstall>/Platform/bfpwencrypt -e password', but the output of that only works when I put it in buildforge.conf as an encoded password - when I put it in buildforge.conf as encrypted - with {bfcrypt:alias} I get the errors listed in my first post?

I'm going to have to suggest that you open a PMR for this one and let the support organization dig through the configuration setup to see what is going on.