Hi Ritu,
Can you check your test case that executionEnvironment is using value longer
than 255 characters ?
I'm asking you this because before the patch, CLM allowed to use SaNameT value
up to 256 characters. But in this case CLM removed the last 256th character and
set \0. So SaNameT value is not the same before and after sending to CLM.
After applying the patch, it's allowed to use SaNameT values up to 255
characters like in IMM. Frankly, I have no idea how CLM stored this values in
IMM earlier.
---
** [tickets:#1906] clm: add support for long DN**
**Status:** review
**Milestone:** 5.1.FC
**Created:** Mon Jul 04, 2016 01:10 PM UTC by Zoran Milinkovic
**Last Updated:** Fri Aug 26, 2016 09:33 AM UTC
**Owner:** Zoran Milinkovic
Ticket [#191] introduces support for long DN.
This ticket adds the support for long RDN to CLM.
Today, there is no any reason for the support for long DN in CLM.
The main reason for adding support for long DN is to support long RDN. In
SaClmNode class, safNode attribute may have a hostname which can be up to 63
bytes. Together with prefix "safNode=", RDN exceedes RDN limitation of 64 bytes.
Limit of 255 bytes for DN will still remain after applying the patch. Only long
RDN will be supported.
The same limitation applies to PLM entities in CLM.
---
Sent from sourceforge.net because opensaf-tickets@lists.sourceforge.net is
subscribed to https://sourceforge.net/p/opensaf/tickets/
To unsubscribe from further messages, a project admin can change settings at
https://sourceforge.net/p/opensaf/admin/tickets/options. Or, if this is a
mailing list, you can unsubscribe from the mailing list.
------------------------------------------------------------------------------
_______________________________________________
Opensaf-tickets mailing list
Opensaf-tickets@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/opensaf-tickets
