- Access exclusive content
- Connect with peers
- Share your expertise
- Find support resources
Our community just got stronger! Explore new identity security resources, connect with experts, and discover more ways to learn and collaborate.
09-06-2018 12:05 PM
10-15-2018 03:47 AM
Yes you can, in fact OS User, Client Certificates and IP/Machine restriction can be used with CCP. Make sure basic/windows auth are enabled on your CCP server
10-15-2018 09:16 AM
@Anand Negi Appreciate for the response. do we need to pass the credentials of the OS user every time when script rans ?
10-15-2018 08:05 PM
Since the applicationID will be restricted with an OS User, the script will need to be run by that very OS user else you will receive the authentication failures. I would advice to use Client certificates though (with serial number restriction).
01-11-2019 02:48 PM
@Anand Negi we have SSL cert on CCP server, where can i obtain client certificate serial number ? on app servers ?
01-11-2019 03:36 PM
@Anand Negi we enabled windows Authentication in web server roles on CCP server, and also enabled Windows Authentication enabled under IIS>AIMWebService>V1.1>Windows Authentication>enabled> then select providers under enabled for NTML as provider. do we need to choose NTML or kerberos ? Can you help ?
when i tried with above configuration i'm unable to authenticate and error was OSUser is unauthorized.
Thank in advance.
01-25-2019 07:36 AM
Another option for OS User authentication, from a Unix machine calling CCP, is to use a keytab file for Kerberos authentication. I have to agree with @Anand Negi that certificates are a preferred option.
02-16-2019 10:59 PM
@Anurag . I'm facing the issue currently. I keep getting 401.2 error with OS Restriction (or without it even). The only way it seems to work is if I enable anonymous authentication (which is obviously not recommended). I'm I missing something basic for the Unix setup ? The same thing works for Windows Env
04-11-2019 06:49 AM
What if the application is hosted on AS400 and AS400 is making aim web service call.I would like to restrict that OS user. I tested it by adding the actual (username) to authentication tab and the fetch is not working. I removed all of them fetch is working. Like we add domain\username for windows domain OS user, have anyone come across what would be right parameter that needed to be added to authentication tab for AS400.
04-11-2019 08:38 AM
04-11-2019 09:35 AM
The implementation guide for CCP lists Windows domain OS user and Client Certs as available options. They also list Allowed Machines as a type but I don't consider an allowed list as authentication. @Anurag . Where do you see OS user is not supported for CCP?
04-11-2019 09:46 AM
04-11-2019 09:59 AM
Sounds good and it was a pain to setup. Also, support told us we could not use OS user with Linux but the documents said we could. Everything is very case sensitive as AD and Kerberos handle case sensitivity a bit different. If you can find a Kerberos expert they should be able to get your configuration working.
08-12-2019 02:31 AM
Interesting thread. I enabled certificate based authentication and it works as expected. There are challenges with IP / OS user and specially when the servers are behind load balancer. The document says use ARR as an option for IP but it also mentions that ARR does not work with certificate based authentication enabled.
Has anyone been able to use a combination of certificate and OS user/IP for CCP. Calling application could be Windows/Linux.
Thanks in advance.
12-16-2019 07:51 AM
Hi,
Haven't tried certificate-based authentication, but OS authentication worked for me by doing the following:
Click Accept as Solution to acknowledge that the answer to your question has been provided.
The button appears next to the replies on topics you’ve started. The member who gave the solution and all future visitors to this topic will appreciate it!
These simple actions take just seconds of your time, but go a long way in showing appreciation for community members and the LIVEcommunity as a whole!
The LIVEcommunity thanks you for your participation!

