As it's currently written, it’s hard to tell exactly what you're asking.
See the How to Ask page for help clarifying this question. when i'm trying to access it browser shows ssl/tls error.
2014/10/03 | squid_kerb_auth: gss_accept_sec_context() failed: An unsupported mechanism was requested. Seem that kerberos is ALWAYS not working only on a specific worstation.
2014/10/03 | negotiate_wrapper: Return 'BH gss_accept_sec_context() failed: An unsupported mechanism was requested. The kerberos part of the is: auth_param negotiate program /usr/local/bin/negotiate_wrapper -d --ntlm /usr/bin/ntlm_auth --diagnostics --helper-protocol=squid-2.5-ntlmssp --domain=DOMAIN--kerberos /usr/local/bin/squid_kerb_auth -d -s GSS_C_NO_NAME auth_param negotiate children 10 startup=0 idle=1 auth_param negotiate keep_alive on Please help as i've already searched everywhere a solution that i can't find and i'm not so expert on squid! If i use kerberos from any other pc it works as excepted.
Authorization verifies that access to the resource is allowed, based on the set of claims in the security token and the configured permissions for the resource.
To determine whether authentication or authorization causes an access issue, look closely at the error message in the browser window.
Network Domain= example.local Subnet = 10.0.11.0/24 Proxy Server IP = 10.0.11.11 HOSTNAME = squid.example.local Kerberos computer name = SQUID-K Windows Server 1 IP = 10.0.11.50 HOSTNAME = dc01.example.local Windows Server 2 IP = 10.0.11.51 HOSTNAME = dc02.example.local Windows 7 Machine IP = 10.0.11.100 Hostname = pc01.example.local Prerequisites Client Windows Computers need to have "Enable Integrated Windows Authentication" ticked in Internet Options ⇒ Advanced settings. LOCAL yum install authconfig authconfig --enableshadow --enablemd5 --passalgo=md5 --krb5kdc=ads.example.local \ --krb5realm=EXAMPLE.
One option is JSON Schema, which is both a way to describe the data format, as well as validate it.
Once we merge it, the changes will be reflected on the website the next time it is deployed.
Summary: Because Share Point 2013 recommends claims-based authentication for user access to web applications, this article describes the tools and techniques that you can use to troubleshoot failed claims-based user authentication attempts.
Successful access to a Share Point resource requires both authentication and authorization.
When you are using claims, authentication verifies that the security token is valid.