Project

General

Profile

Actions

Task #3022

closed

OpenAM - send additional request headers User-Agent and X-Forwarded-For when authenticating

Added by Alena Peterová about 3 years ago. Updated almost 3 years ago.

Status:
Closed
Priority:
Normal
Assignee:
Alena Peterová
Target version:
Start date:
12/16/2021
Due date:
% Done:

100%

Estimated time:
Owner:

Description

For using our special "AM-like" custom interface in CAS, send additional headers User-Agent and X-Forwarded-For of the user request.
If X-Forwarded-For is not present, use the user's IP address.

Actions #1

Updated by Alena Peterová about 3 years ago

  • Description updated (diff)
  • Status changed from New to In Progress
  • % Done changed from 0 to 80

Implemented in https://git.bcvsolutions.eu/modules/openam/-/commit/bc9bd41d641aceae98bd5b94e83cce67a869aa87
It contains also increasing CzechIdM version to 11.2 for usage in our project.

Actions #2

Updated by Alena Peterová almost 3 years ago

  • Status changed from In Progress to Resolved

New request headers are set in a new clientType = "CASPROXY", other types are backwards compatible.
One more difference from the OPENAM13 type is the password encoding - in OpenAM13, we used Base64 encoding, which supported even diacritics in passwords. For our specific CAS proxy interface, this encoding must not be done. Passwords with diacritics are not supported for now, because there are some problems when sending non-ASCII characters in headers in the Apache HTTP Client.

Documented in https://wiki.czechidm.com/devel/documentation/adm/openam

Review was done by @kucerar in our project.

Actions #3

Updated by Alena Peterová almost 3 years ago

  • Status changed from Resolved to Closed
  • % Done changed from 80 to 100

Version 2.2.0 successfully released.

Actions

Also available in: Atom PDF