You can create Custom Properties on the Server class to differentiate the Servers and use the same property in these rules.
This is similar to Proxy rules.
This being very new, the best practices I think will be based on the The different authentication mechanism you choose as per your environment
Thank you Rohit. Just so I understand you I would have to do something like the following:
- Create a new global Server property (UAI_OS for example)
- When I import my servers, have that property set (UAI_OS = Linux, Windows, AIX, etc)
- Change my Rules accordingly (If TARGET.UAI_OS = "Linux" then use this server/credentials)
Unfortunately, my current mechanism is failing because both of my Rules are;
if TARGET.NAME != null
So it works on Linux servers (because it checks and OKs that Rule first) but fails on Windows servers.
1 of 1 people found this helpful
Yes, the OS based rules will work
The rules you have specified are same, the first one will always be evaluated as successful, and hence everytime it will use the Linux Authentication ,the first one
Base it on the OS Type is a good idea because I believe most of the environments will have different authentication mechanisms allowed on OS basis.
If you are integrating Provisioning , it will be a better idea to propogate this through the device property and
make this a mandatory Server Property so that for every server, u have this property set.