Some users may be experiencing issues when trying to access customer resources like the Case Portal or the Product Licensing Center. Our team is aware of the issue and is working to resolve it. Click here for more information.
Team,
We have windows & non windows devices for adoption. Credential are different for both kind of devices. we have added both credential in beacon password manager however while running the rule, we have seen wrong credential gets select for devices & result gets failed due to this.
Can you suggest if we can enforce credential based on created rule.
‎Jun 02, 2022 02:08 AM
Hi @durgeshsingh ,
You can apply filters for passwords, so that they can connect/validate only to those systems. IN Password manager click on view\edit on the account and mention the IPs based on the password and check by running the rule again.
‎Jun 02, 2022 08:00 AM
Hi @durgeshsingh ,
You can apply filters for passwords, so that they can connect/validate only to those systems. IN Password manager click on view\edit on the account and mention the IPs based on the password and check by running the rule again.
‎Jun 02, 2022 08:00 AM
we have tried this option but no luck. it was taking random password only.
‎Jun 02, 2022 08:46 AM
Team,
i have created filter with IP address with comma 7 checked filter option in password manager interface. Its working fine.
Is there any option for bulk case.
‎Jun 03, 2022 08:14 AM
I think credentials used for various operations should be based on the "Account type" that is selected when configuring the password:
If you're seeing (for example) a password registered with a type of "Windows domain account" being used when attempting to make an SSH connection to a target device then that would be a little surprising. But I may be misunderstanding how this process works...
‎Jun 07, 2022 07:14 PM - edited ‎Jun 07, 2022 07:16 PM
User | Count |
---|---|
8 | |
6 | |
3 | |
3 |