- **status**: accepted --> review
- **Comment**:

https://sourceforge.net/p/opensaf/mailman/message/33046736/



---

** [tickets:#1206] imm: long DN attribute in search/accerror result must cope 
with client capabilities.**

**Status:** review
**Milestone:** 4.5.1
**Created:** Mon Nov 10, 2014 03:40 PM UTC by Zoran Milinkovic
**Last Updated:** Wed Nov 12, 2014 11:21 AM UTC
**Owner:** Zoran Milinkovic

Long DN attribute values are not handled well if a client does not support
long DNs.

In searchNext, the client can get long DN values in object name and SaNameT 
attributes.
In accessorGet, the client can get long DN values in SaNameT attributes.
OI callbacks can get long DN values in SaNameT attributes.

If searchNext and accessorGet have long DN in the result, functions will not 
return any result, and the error code will be SA_AIS_ERR_NAME_TOO_LONG. This 
error code will not break the search, and the client can continue with next 
search result.

If OI callback contains long DN in its parameters, OI callback will not be 
processed up to the client, and the library will return appropriate error code.


---

Sent from sourceforge.net because [email protected] 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.
------------------------------------------------------------------------------
Download BIRT iHub F-Type - The Free Enterprise-Grade BIRT Server
from Actuate! Instantly Supercharge Your Business Reports and Dashboards
with Interactivity, Sharing, Native Excel Exports, App Integration & more
Get technology previously reserved for billion-dollar corporations, FREE
http://pubads.g.doubleclick.net/gampad/clk?id=157005751&iu=/4140/ostg.clktrk
_______________________________________________
Opensaf-tickets mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/opensaf-tickets

Reply via email to