fighting for truth, justice, and a kick-butt lotus notes experience.

HCL SafeLinx 1.2.0 IF1 released

Detlev Poettgen  August 10 2021 08:22:22 AM

HCL released a fix for HCL Safelinx this week.

The build number is SafeLinx 1.2.0.1 (IF1)

Beside fixes there are a few new features included, like:

- MySQL on Windows support.
- Enable Windows SAML HTTP authentication
- Add redirect function to Nomad for / and /nomad paths to send to /nomad/index.html.


Included fixes:


SAFE-799:
MySQL on Windows support.


SAFE-820:
Add charset=utf-8 for json responses to fix character issues.


SAFE-821:
Nomad, parsing of CORS Origin header token may fail causing transaction failures.


SAFE-822:
Hidden option to disable CORS origin validation.


SAFE-823:
Nomad specific login screen translations missing in Linux pkg.


SAFE-841:
Crash in client-less processing code when Locale or Accept-Lang is not set.


SAFE-844:
SafeLinx Server Shutdown after Administrator window close and the Server Process start/stop not working from Administrator.


SAFE-851:
Buffer overrun in javascript rewrite function for client-less access with URL rewriting enabled.


SAFE-857:
Issue with converting the users home mailserver to canonical format when it contains multiple instances of the same attribute.


SAFE-865:
Default to a domino server in the app server list if no home mail server is defined for a Nomad user.


SAFE-867:
Remove expired ltpatokens from Cookie when multiple exist and SL can decode them. Block 3rd party token generation and set when SafeLinx is using token as SID.


SAFE-873:
When creating userConfig.json, if the user CN value has an attr with 2 or less characters, conversion to canonical format will fail leaving an invalid userCN in the json.


SAFE-886:
Ltpa config that users OtherID with X.500 notation transform fails when verifying username in unknown user scenario.


SAFE-887:
Performance issue when LtpaToken configured to use Other ID from directory record. Non indexed searches can lead to delays in transaction processing.


SAFE-885:
Add Server-Worker-Allowed to Nomad static file downloads.


SAFE-913:
Add redirect function to Nomad for / and /nomad paths to send to /nomad/index.html.


SAFE-918:
Server fails to start after reboot. Old autorestart scripts causing exit when used with systemd.


SAFE-935:
Default HTTP certificate file missing from Windows install.


SAFE-936:
Server startup fails if HTTP certificate file is missing.


SAFE-937:
Remove MFA-id check from nomad standard_login.html form.


SAFE-939:
Enable Windows SAML HTTP authentication


Details can be found here:

https://support.hcltechsw.com/csm?id=kb_article_view&sys_kb_id=f047e5dd876170105440c9d8cebb3573

Kommentare
noch keine Kommentare vorhanden
  •  
  • Hinweis zum Datenschutz und Datennutzung:
    Bitte lesen Sie unseren Hinweis zum Datenschutz bevor Sie hier einen Kommentar erstellen.
    Zur Erstellung eines Kommentar werden folgende Daten benötigt:
    - Name
    - Mailadresse
    Der Name kann auch ein Nickname/Pseudonym sein und wird hier auf diesem Blog zu Ihrem Kommentar angezeigt. Die Email-Adresse dient im Fall einer inhaltlichen Unklarheit Ihres Kommentars für persönliche Rückfragen durch mich, Detlev Pöttgen.
    Sowohl Ihr Name als auch Ihre Mailadresse werden nicht für andere Zwecke (Stichwort: Werbung) verwendet und auch nicht an Dritte übermittelt.
    Ihr Kommentar inkl. Ihrer übermittelten Kontaktdaten kann jederzeit auf Ihren Wunsch hin wieder gelöscht werden. Senden Sie in diesem Fall bitte eine Mail an blog(a)poettgen(punkt)eu

  • Note on data protection and data usage:
    Please read our Notes on Data Protection before posting a comment here.
    The following data is required to create a comment:
    - Name
    - Mail address
    The name can also be a nickname/pseudonym and will be displayed here on this blog with your comment. The email address will be used for personal questions by me, Detlev Pöttgen, in the event that the content of your comment is unclear.
    Neither your name nor your e-mail address will be used for any other purposes (like advertising) and will not be passed on to third parties.
    Your comment including your transmitted contact data can be deleted at any time on your request. In this case please send an email to blog(a)poettgen(dot)eu

Treffpunkte

Archive