Skip to content

Commit

Permalink
Added CAS v3.0 references where appropriate
Browse files Browse the repository at this point in the history
  • Loading branch information
Blair Allen committed Jul 1, 2019
1 parent cefaf55 commit b2e7975
Show file tree
Hide file tree
Showing 5 changed files with 13 additions and 11 deletions.
15 changes: 8 additions & 7 deletions DotNetCasClient/CasAuthentication.cs
Original file line number Diff line number Diff line change
Expand Up @@ -848,14 +848,15 @@ internal static bool ProcessProxyCallbackRequest()

/// <summary>
/// Validates a ticket contained in the URL, presumably generated by
/// the CAS server after a successful authentication. The actual ticket
/// the CAS server after a successful authentication. The actual ticket
/// validation is performed by the configured TicketValidator
/// (i.e., CAS 1.0, CAS 2.0, SAML 1.0). If the validation succeeds, the
/// request is authenticated and a FormsAuthenticationCookie and
/// corresponding CasAuthenticationTicket are created for the purpose of
/// authenticating subsequent requests (see ProcessTicketValidation
/// method). If the validation fails, the authentication status remains
/// unchanged (generally the user is and remains anonymous).
/// (i.e., CAS 1.0, CAS 2.0, CAS 3.0, SAML 1.0). If the validation
/// succeeds, the request is authenticated and a
/// FormsAuthenticationCookie and corresponding CasAuthenticationTicket
/// are created for the purpose of authenticating subsequent requests
/// (see ProcessTicketValidation method). If the validation fails, the
/// authentication status remains unchanged (generally the user is and
/// remains anonymous).
/// </summary>
internal static void ProcessTicketValidation()
{
Expand Down
Original file line number Diff line number Diff line change
Expand Up @@ -100,7 +100,7 @@ protected override ICasPrincipal ParseResponseFromServer(string response, string
}
catch (InvalidOperationException)
{
throw new TicketValidationException("CAS Server response does not conform to CAS 2.0/3.0 schema");
throw new TicketValidationException("CAS Server response does not conform to CAS 3.0 schema");
}

if (serviceResponse.IsAuthenticationSuccess)
Expand Down
Original file line number Diff line number Diff line change
Expand Up @@ -65,6 +65,7 @@ string ServiceParameterName
/// <list>
/// <item>CAS 1.0: validate</item>
/// <item>CAS 2.0: serviceValidate or proxyValidate</item>
/// <item>CAS 3.0: p3/serviceValidate or p3/proxyValidate</item>
/// <item>SAML 1.1: samlValidate</item>
/// </list>
/// </summary>
Expand Down
4 changes: 2 additions & 2 deletions ExampleWebSite/web.config.sample
Original file line number Diff line number Diff line change
Expand Up @@ -56,7 +56,7 @@
- casServerUrlPrefix
URL to root of CAS server application.
- ticketValidatorName
Supported values: Cas10, Cas20, and Saml11.
Supported values: Cas10, Cas20, Cas30, and Saml11.
Name of ticket validator that validates CAS tickets using a particular protocol.
Optional Attributes:
Expand Down Expand Up @@ -116,7 +116,7 @@
renew="false"
singleSignOut="true"
ticketTimeTolerance="5000"
ticketValidatorName="Cas20"
ticketValidatorName="Cas30"
proxyTicketManager="CacheProxyTicketManager"
serviceTicketManager="CacheServiceTicketManager"
gatewayStatusCookieName="CasGatewayStatus" />
Expand Down
2 changes: 1 addition & 1 deletion README.md
Original file line number Diff line number Diff line change
Expand Up @@ -15,7 +15,7 @@ The Apereo .NET CAS client provides CAS integration for the Microsoft Windows pl

## Features ##

- Supports CAS Protocol 1.0 and 2.0 and SAML 1.1
- Supports CAS Protocol 1.0, 2.0, and 3.0 and SAML 1.1
- Supports CAS single sign-out
- Rich support for Microsoft ASP.NET platform integration through Forms Authentication framework

Expand Down

0 comments on commit b2e7975

Please sign in to comment.