Appreciate the detailed breakdown! I have a quick question: I have a SafePal wallet with USDT, and I have the seed phrase. (alarm fetch churn bridge exercise tape speak race clerk couch crater letter). Could you explain how to move them to Binance?
@@technicalthings3741 In CI/CD Pipelines: Jenkins: Use Jenkins Credentials Manager GitHub Actions: Use GitHub Secrets GitLab CI: Use GitLab CI/CD Variables Azure DevOps: Use Variable Groups/Library For Local Development: Environment Variables Local .env files (added to .gitignore) Local secure credential stores
you can store secret key as environment variables or key manager on the test execution machine or on you local machine. No need to expose it in your prop file. Best approach is always to maintain keys and password/tokens as environment variables.
I'll say yes its possible. Hence performing the encryption or decryption in test automation for app passwords, is not a perfect approach. But these are lower environment passwords not for the PROD. Always maintain the token and secrets in the secret key on your test automation machine or part of CI CD pipeline. In CI/CD Pipelines: Jenkins: Use Jenkins Credentials Manager GitHub Actions: Use GitHub Secrets GitLab CI: Use GitLab CI/CD Variables Azure DevOps: Use Variable Groups/Library For Local Development: Environment Variables Local .env files (added to .gitignore) Local secure credential stores
Please make a video on how to byepass default loading page in selenium. According to organization policy , org page will load by deafult. Used edge options user dir path set. And added profile. However profile page is not signed in , Any ideas??
So the first time when we encrypt the password , we are going to pass the password to encrypt , so where are we going to fetch that password from, we will have to store it somewhere , right ?
Hi naveen sir I have created hybrid framework with page object model pattern with pytest and bdd framework with page object model.I request to look at both framework tell me that i am in a proper direction.I will share github links for both the projects. tell me that is both projects are per current industry ? Can you please share your mail id?
you can store secret key as environment variables or key manager on the test execution machine or on you local machine. No need to expose it in your code. Without secret key, one can never decrypt the password.
@@naveenautomationlabs Great question! If you're concerned about exposing passwords in your code, the best approach is to store passwords securely in environment variables or a password manager (like AWS Secrets Manager or HashiCorp Vault). These methods are secure, simple, and efficient. Why not use encryption? Encryption adds unnecessary complexity and performance overhead. Password managers and environment variables already provide automatic encryption and access control, so you don’t need to handle encryption yourself. The key to security is access control: only authorized processes should have access to the password, which these tools manage effectively. In short, storing passwords in secure locations like environment variables or password managers is both the easiest and safest way to protect your credentials, without the added complexity of encryption.
One of the most awaited video , thanks Naveen your doing great job for testers community
Thanks Naveen Sir for explaining the Password Masking.
Appreciate the detailed breakdown! I have a quick question: I have a SafePal wallet with USDT, and I have the seed phrase. (alarm fetch churn bridge exercise tape speak race clerk couch crater letter). Could you explain how to move them to Binance?
Usually secrets should be from pipeline run it should not be hard-coded in code
@@mohamedsulaimaansheriff9787 how.can you explain in detail
@@technicalthings3741
In CI/CD Pipelines:
Jenkins: Use Jenkins Credentials Manager
GitHub Actions: Use GitHub Secrets
GitLab CI: Use GitLab CI/CD Variables
Azure DevOps: Use Variable Groups/Library
For Local Development:
Environment Variables
Local .env files (added to .gitignore)
Local secure credential stores
Hi Naveen...I am looking forward to join an API testing course. Are you starting any api testing batch? If yes , please let me know
Let's say we store key as well encrypted password in properties file, but that can again be easily decrypted by anyone ..right?
You are correct. I was also thinking the same 😅
you can store secret key as environment variables or key manager on the test execution machine or on you local machine. No need to expose it in your prop file.
Best approach is always to maintain keys and password/tokens as environment variables.
Can you please create a video on vault integration.. it ll be very helpful
True sir, but it’s very easy to decrypt and see the password as method is available.How can we hide decryption logic?
I'll say yes its possible. Hence performing the encryption or decryption in test automation for app passwords, is not a perfect approach.
But these are lower environment passwords not for the PROD.
Always maintain the token and secrets in the secret key on your test automation machine or part of CI CD pipeline.
In CI/CD Pipelines:
Jenkins: Use Jenkins Credentials Manager
GitHub Actions: Use GitHub Secrets
GitLab CI: Use GitLab CI/CD Variables
Azure DevOps: Use Variable Groups/Library
For Local Development:
Environment Variables
Local .env files (added to .gitignore)
Local secure credential stores
@ thanks so much sir for your quick response. You are amazing⭐️
Please make a video on how to byepass default loading page in selenium. According to organization policy , org page will load by deafult. Used edge options user dir path set. And added profile. However profile page is not signed in , Any ideas??
after decrypting if some one just print it then he can know the password? decryption is needed to use in send key method..
So the first time when we encrypt the password , we are going to pass the password to encrypt , so where are we going to fetch that password from, we will have to store it somewhere , right ?
And what if someone debug the decryped pwd?
It's mandatory to use the Encryption of password in Automation??
We can keep it in Jenkins secrets
Hi naveen sir
I have created hybrid framework with page object model pattern with pytest and bdd framework with page object model.I request to look at both framework tell me that i am in a proper direction.I will share github links for both the projects.
tell me that is both projects are per current industry ?
Can you please share your mail id?
Anyone can decrypted password from properties file
you can store secret key as environment variables or key manager on the test execution machine or on you local machine. No need to expose it in your code.
Without secret key, one can never decrypt the password.
@@naveenautomationlabs
Great question! If you're concerned about exposing passwords in your code, the best approach is to store passwords securely in environment variables or a password manager (like AWS Secrets Manager or HashiCorp Vault). These methods are secure, simple, and efficient.
Why not use encryption?
Encryption adds unnecessary complexity and performance overhead.
Password managers and environment variables already provide automatic encryption and access control, so you don’t need to handle encryption yourself.
The key to security is access control: only authorized processes should have access to the password, which these tools manage effectively.
In short, storing passwords in secure locations like environment variables or password managers is both the easiest and safest way to protect your credentials, without the added complexity of encryption.