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

IBM Mobile Connect - New Fix for 6.1.5.1 available

 6 Mai 2014 21:03:40
Today IBM released a new Interims Fix for IBM Mobile Connect 6.1.5.1.

If you are running multiple Traveler HA Pools, then you should take a look into IV59618.
We are now able to use a single URL for all of our Pools. IMC supports using a LDAP Attribute to assign a new user to a specific defined Pool. That's a smart solution.

From the APAR list, which can be found here: List of APAR fixes for IBM Mobile Connect 6.1.5.1

IV56448
Add support for blocking attachments in iNotes.
20140318
IV56865
HTTP-AS fails to enforce application server definitions after 
first connect. If server restriction of specific path prefix is not guaranteed.
20140321
IV56925
iNotes / Sametime integration broken in 6151. Fails to decompress
the iNotes configuration file without URL rewriting enabled.
20140321
IV57302
HTTP-AS performance improvements when downloading large files.
20140409
IV58757
HTTP-AS, certificate only authentication, first transaction 
does not include the single sign-on token.
20140409
IV58761
Port setting when SSO is enabled is not appended to the Ltpa
token realm.
20140409
IV58777
Cross-Site scripting vulnerability for old browsers that don't
enforce UTF-8 charsets.
20140409
IV59269
Add a special case hander to iNotes ALG for processing IBM Docs
viewers.
20140416
IV58779
Add ability to send RADIUS challenge / response message to 
client when prompting for soft tokens and provide ability
to display login failure messages from RADIUS.
20140422
IV59618
Add configurable attribute to allow IMC to retrieve a hint
as to which traveler pool or server a new user should be 
assigned to.
20140505
IV60066
Secure only bit on SSO configuration for authentication
methods is not being honored.
20140505
IV60141
Bug introduced by IV59618, crash processing multiple bad login due to bad password requests for the same user.
20140506



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

Archive