oruff1 Absent Member.
Absent Member.
837 views

Issues when working with Dates


Hello,

I would like to import the following LDAP attributes for Users:
*DirXML-HireDate
DirXML-FirstWorkingDay
DirXML-TerminationDate
DirXML-LastWorkingDay
*

All are using the syntax *Generalized Time (OID
1.3.6.1.4.1.1466.115.121.1.24)*

This is the exact same syntax as attribute *lastLoginTime*

I've created User attributes with the Data Type of "DATE"

When I run the Collection I get the following error: *Error validating
attribute value type to it's data type*

From the table arops.error_attribute, I'm able to see:
id; attribute_key; attribute_value; err_stack_trace; error_message;
severity;
11030;"HireDate";"20150728200000Z";"";"Error validating attribute value
type to it's data type";"WARNING";11029

So, I've probably messed something some where, but can't see what.

The same applies for Accounts.
I'm trying to import Last Login Date from an Oracle DB.
I've tried many combinations ... and couldn't find the right one ...


Any help welcome.
Thanks in advance.


--
oruff
------------------------------------------------------------------------
oruff's Profile: https://forums.netiq.com/member.php?userid=9517
View this thread: https://forums.netiq.com/showthread.php?t=54006

0 Likes
4 Replies
Anonymous_User Absent Member.
Absent Member.

Re: Issues when working with Dates

On 08/10/2015 11:25 AM, oruff wrote:
>
> Hello,
>
> I would like to import the following LDAP attributes for Users:
> *DirXML-HireDate
> DirXML-FirstWorkingDay
> DirXML-TerminationDate
> DirXML-LastWorkingDay
> *
>
> All are using the syntax *Generalized Time (OID
> 1.3.6.1.4.1.1466.115.121.1.24)*
>
> This is the exact same syntax as attribute *lastLoginTime*
>
> I've created User attributes with the Data Type of "DATE"
>
> When I run the Collection I get the following error: *Error validating
> attribute value type to it's data type*
>
> From the table arops.error_attribute, I'm able to see:
> id; attribute_key; attribute_value; err_stack_trace; error_message;
> severity;
> 11030;"HireDate";"20150728200000Z";"";"Error validating attribute value
> type to it's data type";"WARNING";11029
>
> So, I've probably messed something some where, but can't see what.
>
> The same applies for Accounts.
> I'm trying to import Last Login Date from an Oracle DB.
> I've tried many combinations ... and couldn't find the right one ...
>
>
> Any help welcome.
> Thanks in advance.
>
>

Greetings,
Since you are working with GTS (Support) and now with me, this will
be answered there.

--

Sincerely,
Steven Williams
Lead Software Engineer
Micro Focus
0 Likes
Knowledge Partner Knowledge Partner
Knowledge Partner

Re: Issues when working with Dates

On 08/10/2015 09:25 AM, oruff wrote:
>
> I would like to import the following LDAP attributes for Users:
> *DirXML-HireDate
> DirXML-FirstWorkingDay
> DirXML-TerminationDate
> DirXML-LastWorkingDay
> *
>
> All are using the syntax *Generalized Time (OID
> 1.3.6.1.4.1.1466.115.121.1.24)*


Within the eDirectory (LDAP) environment, I believe this is probably true,
yes.

> This is the exact same syntax as attribute *lastLoginTime*


It may be worth pointing out that lastLoginTime (as seen via LDAP) is an
operation property, not an attribute, but that does not change its syntax,
just how it is retrieved by clients sometimes. This also assumes the
property has a value,j since a user who has not logged in (common enough
in a vault) may not have one.

> I've created User attributes with the Data Type of "DATE"
>
> When I run the Collection I get the following error: *Error validating
> attribute value type to it's data type*


Which collector is doing this?

> From the table arops.error_attribute, I'm able to see:
> id; attribute_key; attribute_value; err_stack_trace; error_message;
> severity;
> 11030;"HireDate";"20150728200000Z";"";"Error validating attribute value
> type to it's data type";"WARNING";11029
>
> So, I've probably messed something some where, but can't see what.
>
> The same applies for Accounts.
> I'm trying to import Last Login Date from an Oracle DB.
> I've tried many combinations ... and couldn't find the right one ...


When pulling in from the database what is the column's defined
format/syntax and do all rows have a value or could you be hitting
something NULL?

--
Good luck.

If you find this post helpful and are logged into the web interface,
show your appreciation and click on the star below...
0 Likes
Anonymous_User Absent Member.
Absent Member.

Re: Issues when working with Dates

On 08/11/2015 08:41 AM, ab wrote:
> On 08/10/2015 09:25 AM, oruff wrote:
>>
>> I would like to import the following LDAP attributes for Users:
>> *DirXML-HireDate
>> DirXML-FirstWorkingDay
>> DirXML-TerminationDate
>> DirXML-LastWorkingDay
>> *
>>
>> All are using the syntax *Generalized Time (OID
>> 1.3.6.1.4.1.1466.115.121.1.24)*

>
> Within the eDirectory (LDAP) environment, I believe this is probably true,
> yes.
>
>> This is the exact same syntax as attribute *lastLoginTime*

>
> It may be worth pointing out that lastLoginTime (as seen via LDAP) is an
> operation property, not an attribute, but that does not change its syntax,
> just how it is retrieved by clients sometimes. This also assumes the
> property has a value,j since a user who has not logged in (common enough
> in a vault) may not have one.
>
>> I've created User attributes with the Data Type of "DATE"
>>
>> When I run the Collection I get the following error: *Error validating
>> attribute value type to it's data type*

>
> Which collector is doing this?
>
>> From the table arops.error_attribute, I'm able to see:
>> id; attribute_key; attribute_value; err_stack_trace; error_message;
>> severity;
>> 11030;"HireDate";"20150728200000Z";"";"Error validating attribute value
>> type to it's data type";"WARNING";11029
>>
>> So, I've probably messed something some where, but can't see what.
>>
>> The same applies for Accounts.
>> I'm trying to import Last Login Date from an Oracle DB.
>> I've tried many combinations ... and couldn't find the right one ...

>
> When pulling in from the database what is the column's defined
> format/syntax and do all rows have a value or could you be hitting
> something NULL?
>

Greetings,
This is not an "issue" but rather configuration.

--

Sincerely,
Steven Williams
Lead Software Engineer
Micro Focus
0 Likes
Knowledge Partner Knowledge Partner
Knowledge Partner

Re: Issues when working with Dates

Name it whatever.

Copying an existing collector and then modifying it by adding something to
the input transformation scripts may help if there is a formatting
configuration issue among systems. It'd be great if there were a trace
like with the IDM engine showing values as they came in, were transformed,
etc., though I do not know of that level of sophistication yet in Access
Review (it's only at version 1.1 after all, where the engine is at 4.5).

--
Good luck.

If you find this post helpful and are logged into the web interface,
show your appreciation and click on the star below...
0 Likes
The opinions expressed above are the personal opinions of the authors, not of Micro Focus. By using this site, you accept the Terms of Use and Rules of Participation. Certain versions of content ("Material") accessible here may contain branding from Hewlett-Packard Company (now HP Inc.) and Hewlett Packard Enterprise Company. As of September 1, 2017, the Material is now offered by Micro Focus, a separately owned and operated company. Any reference to the HP and Hewlett Packard Enterprise/HPE marks is historical in nature, and the HP and Hewlett Packard Enterprise/HPE marks are the property of their respective owners.