Anonymous_User Absent Member.
Absent Member.

Re: Google driver to handle new APIs?


Following on from my previous post, I've come across another issue
whereby the customer currently has a Matching Policy setup on the Google
Apps driver which specifies to only match on UniqueID -> mapped to
UserName attribute in Google Apps. In the trace however, the driver
tries to match on both "UserName" and "email" attributes in Google Apps,
even though email is never specified. When an email value cannot be
found (i.e. returns false), the the driver throws a 'fatal' error,
returns a null pointer exception, and switches off.

Not sure why the driver adds in the matching criteria for email
attribute value, and not sure why the "Find Matching Object" can crash
the driver when returning false as it's supposed, but I assume this to
be a bug.

I've put the trace of the Matching Policy below. Any help would be
great.

Regards,
Ryan


Code:
--------------------
15:31:47 155C Drvrs: GAPPSDRV ST:Applying policy: UOFAGGLEUSER-sub-mp-DefaultMatch.
15:31:47 155C Drvrs: GAPPSDRV ST: Applying to add #1.
15:31:47 155C Drvrs: GAPPSDRV ST: Evaluating selection criteria for rule 'Match User'.
15:31:47 155C Drvrs: GAPPSDRV ST: (if-class-name equal "User") = TRUE.
15:31:47 155C Drvrs: GAPPSDRV ST: (if-op-attr 'Services' equal "EMAIL_SUFFIX_@student.adelaide.edu.au") = TRUE.
15:31:47 155C Drvrs: GAPPSDRV ST: (if-op-attr 'Internet Email Address' available) = TRUE.
15:31:47 155C Drvrs: GAPPSDRV ST: Rule selected.
15:31:47 155C Drvrs: GAPPSDRV ST: Applying rule 'Match User'.
15:31:47 155C Drvrs: GAPPSDRV ST: Action: do-find-matching-object(scope="subtree",arg-match-attr("UserName",token-src-name())).
15:31:47 155C Drvrs: GAPPSDRV ST: arg-match-attr("UserName",token-src-name())
15:31:47 155C Drvrs: GAPPSDRV ST: arg-string(token-src-name())
15:31:47 155C Drvrs: GAPPSDRV ST: token-src-name()
15:31:47 155C Drvrs: GAPPSDRV ST: Token Value: "a9810004".
15:31:47 155C Drvrs: GAPPSDRV ST: Arg Value: "a9810004".
15:31:47 155C Drvrs: GAPPSDRV ST: Query from policy
15:31:47 155C Drvrs: GAPPSDRV ST:
<nds dtdversion="4.0" ndsversion="8.x">
<source>
<product edition="Standard" version="4.0.2.1">DirXML</product>
<contact>Novell, Inc.</contact>
</source>
<input>
<query class-name="User" scope="subtree">
<search-class class-name="User"/>
<search-attr attr-name="UserName">
<value>a9810004</value>
</search-attr>
<read-attr/>
</query>
</input>
</nds>
15:31:47 155C Drvrs: GAPPSDRV ST: Fixing up association references.
15:31:47 155C Drvrs: GAPPSDRV ST: Applying schema mapping policies to output.
15:31:47 155C Drvrs: GAPPSDRV ST: Applying policy: UOFAGGLEBCFG-sch_SchemaMap.
15:31:47 155C Drvrs: GAPPSDRV ST: Mapping class-name 'User' to 'UserEntry'.
15:31:47 155C Drvrs: GAPPSDRV ST: Mapping class-name 'User' to 'UserEntry'.
15:31:47 155C Drvrs: GAPPSDRV ST: No output transformation policies.
15:31:47 155C Drvrs: GAPPSDRV ST: Submitting document to subscriber shim:
15:31:47 155C Drvrs: GAPPSDRV ST:
<nds dtdversion="4.0" ndsversion="8.x">
<source>
<product edition="Standard" version="4.0.2.1">DirXML</product>
<contact>Novell, Inc.</contact>
</source>
<input>
<query class-name="UserEntry" event-id="0" scope="subtree">
<search-class class-name="UserEntry"/>
<search-attr attr-name="UserName">
<value>a9810004</value>
</search-attr>
<read-attr/>
</query>
</input>
</nds>
15:31:47 155C Drvrs: GAPPSDRV ST: execute
15:31:47 155C Drvrs: GAPPSDRV ST:
<nds dtdversion="4.0" ndsversion="8.x">
<source>
<product edition="Standard" version="4.0.2.1">DirXML</product>
<contact>Novell, Inc.</contact>
</source>
<input>
<query class-name="UserEntry" event-id="0" scope="subtree">
<search-class class-name="UserEntry"/>
<search-attr attr-name="UserName">
<value>a9810004</value>
</search-attr>
<read-attr/>
</query>
</input>
</nds>
15:31:47 155C Drvrs: GAPPSDRV ST: connect
15:31:47 155C Drvrs: GAPPSDRV ST: dispatch
15:31:47 155C Drvrs: GAPPSDRV ST: queryHandler
15:31:47 155C Drvrs: GAPPSDRV ST: queryHandler: association == null
15:31:47 155C Drvrs: GAPPSDRV ST: queryHandler: class-name == 'UserEntry'
15:31:47 155C Drvrs: GAPPSDRV ST: queryHandler: event-id == '0'
15:31:47 155C Drvrs: GAPPSDRV ST: queryHandler: max-result-count == 2147483647
15:31:47 155C Drvrs: GAPPSDRV ST: queryHandler: qualified-src-dn == null
15:31:47 155C Drvrs: GAPPSDRV ST: queryHandler: scope == 'subtree'
15:31:47 155C Drvrs: GAPPSDRV ST: queryHandler: src-dn == null
15:31:47 155C Drvrs: GAPPSDRV ST: queryHandler: src-entry-id == null
15:31:47 155C Drvrs: GAPPSDRV ST: queryHandler: search-attr: UserName. Value = a9810004
15:31:47 155C Drvrs: GAPPSDRV ST: queryHandler: contains query token? false
15:31:47 155C Drvrs: GAPPSDRV ST: queryHandler: contains read attrs? false
15:31:47 155C Drvrs: GAPPSDRV ST: queryHandler: contains search attrs? true
15:31:47 155C Drvrs: GAPPSDRV ST: queryHandler: contains search classes? true
15:31:47 155C Drvrs: GAPPSDRV ST: queryHandler: has entry scope? false
15:31:47 155C Drvrs: GAPPSDRV ST: queryHandler: has subordinates scope? false
15:31:47 155C Drvrs: GAPPSDRV ST: queryHandler: has subtree scope? true
15:31:47 155C Drvrs: GAPPSDRV ST: queryHandler: has limited results? false
15:31:47 155C Drvrs: GAPPSDRV ST: queryHandler: has unlimited results? true
15:31:47 155C Drvrs: GAPPSDRV ST: queryHandler: has root base object? true
15:31:47 155C Drvrs: GAPPSDRV ST: queryHandler: is cancelled query? false
15:31:47 155C Drvrs: GAPPSDRV ST: queryHandler: is extended query? false
15:31:47 155C Drvrs: GAPPSDRV ST: queryHandler: is identity query? false
15:31:47 155C Drvrs: GAPPSDRV ST: queryHandler: is initial query? true
15:31:47 155C Drvrs: GAPPSDRV ST: queryHandler: is subsequent query? false
15:31:47 155C Drvrs: GAPPSDRV ST: queryHandler: should read attrs? false
15:31:47 155C Drvrs: GAPPSDRV ST: queryHandler: should read parent? false
15:31:47 155C Drvrs: GAPPSDRV ST: queryHandler: should search all classes? false
15:31:47 155C Drvrs: GAPPSDRV ST: Processing search criteria
15:31:47 155C Drvrs: GAPPSDRV ST: Query for User object
15:31:47 155C Drvrs: GAPPSDRV ST: Search Attribute: UserName
15:31:47 155C Drvrs: GAPPSDRV ST: Association: null
15:31:47 155C Drvrs: GAPPSDRV ST: GMailDriver queryHandler(): search-attr = UserName
15:31:47 155C Drvrs: GAPPSDRV ST: GMailDriver queryHandler(): search-attr = email
15:31:47 155C Drvrs: GAPPSDRV ST: DirectoryAppClient.isEmailAddressFormat(): validating a9810004
15:31:47 155C Drvrs: GAPPSDRV ST: DirectoryAppClient.isEmailAddressFormat(): returning false
15:31:47 155C Drvrs: GAPPSDRV ST: DirectoryAppClient.isEmailAddressFormat(): validating a9810004
15:31:47 155C Drvrs: GAPPSDRV ST: DirectoryAppClient.isEmailAddressFormat(): returning false
15:31:47 155C Drvrs: GAPPSDRV ST: GMailDriver queryHandler(): search value == null
15:31:47 155C Drvrs: GAPPSDRV ST: SubscriptionShim.execute() returned:
15:31:47 155C Drvrs: GAPPSDRV ST:
<nds dtdversion="3.0">
<source>
<product build="20150319_1650" instance="IDM4 Google Apps Driver" version="4.0.4.0">GoogleApps Driver</product>
<contact>NetIQ Corporation</contact>
</source>
<output>
<status event-id="0" level="fatal" type="driver-status">
<description>java.lang.NullPointerException</description>
<exception class-name="java.lang.NullPointerException">
<stack-trace>java.lang.NullPointerException
at com.novell.nds.dirxml.driver.gmailshim.CommonImpl.queryHandler(CommonImpl.java:2193)
at com.novell.nds.dirxml.driver.gmailshim.GMailSubscriptionShim.dispatch(GMailSubscriptionShim.java:640)
at com.novell.nds.dirxml.driver.gmailshim.GMailSubscriptionShim.execute(GMailSubscriptionShim.java:485)
at com.novell.nds.dirxml.engine.Subscriber.execute(Subscriber.java:448)
at com.novell.nds.dirxml.engine.Subscriber.execute(Subscriber.java:282)
at com.novell.nds.dirxml.engine.Subscriber$SubscriberAppQueryProcessor.query(Subscriber.java:2073)
at com.novell.nds.dirxml.driver.XdsQueryProcessor.query(XdsQueryProcessor.java:84)
at com.novell.nds.dirxml.engine.rules.DoFindMatchingObject.apply(DoFindMatchingObject.java:177)
at com.novell.nds.dirxml.engine.rules.ActionSet.apply(ActionSet.java:180)
at com.novell.nds.dirxml.engine.rules.DirXMLScriptProcessor.applyRules(DirXMLScriptProcessor.java:307)
at com.novell.nds.dirxml.engine.Subscriber$AddProcessor.process(Subscriber.java:1306)
at com.novell.nds.dirxml.engine.Subscriber$ModifyProcessor.process(Subscriber.java:1496)
at com.novell.nds.dirxml.engine.Subscriber.processEvent(Subscriber.java:1102)
at com.novell.nds.dirxml.engine.Subscriber.processEvents(Subscriber.java:946)

15:31:47 155C Drvrs: at com.novell.nds.dirxml.engine.Driver.submitTransaction(Driver.java:628)
at com.novell.nds.dirxml.engine.DriverEntry.submitTransaction(DriverEntry.java:1065)
at com.novell.nds.dirxml.engine.DriverEntry.processCachedTransaction(DriverEntry.java:949)
at com.novell.nds.dirxml.engine.DriverEntry.eventLoop(DriverEntry.java:771)
at com.novell.nds.dirxml.engine.DriverEntry.run(DriverEntry.java:561)
at java.lang.Thread.run(Unknown Source)
</stack-trace>
</exception>
<document xml:space="preserve"><nds dtdversion="4.0" ndsversion="8.x">
<source>
<product edition="Standard" version="4.0.2.1">DirXML</product>
<contact>Novell, Inc.</contact>
</source>
<input>
<query class-name="UserEntry" event-id="0" scope="subtree">
<search-class class-name="UserEntry"/>
<search-attr attr-name="UserName">
<value>a9810004</value>
</search-attr>
<read-attr/>
</query>
</input>
</nds></document>
</status>
</output>
</nds>
--------------------


--
rdenys
------------------------------------------------------------------------
rdenys's Profile: https://forums.netiq.com/member.php?userid=5605
View this thread: https://forums.netiq.com/showthread.php?t=51906

0 Likes
Anonymous_User Absent Member.
Absent Member.

Re: Google driver to handle new APIs?

On Wed, 08 Apr 2015 10:34:01 +0000, rdenys wrote:

> Following on from my previous post, I've come across another issue
> whereby the customer currently has a Matching Policy setup on the Google
> Apps driver which specifies to only match on UniqueID -> mapped to
> UserName attribute in Google Apps. In the trace however, the driver
> tries to match on both "UserName" and "email" attributes in Google Apps,
> even though email is never specified. When an email value cannot be
> found (i.e. returns false), the the driver throws a 'fatal' error,
> returns a null pointer exception, and switches off.


Weird. I don't recall seeing that here. I do see the search for 'email',
I'm guessing that's a feature, not a bug, but mine doesn't throw a null
pointer exception when it doesn't find anything. Lacking any really good
ideas here, I think you need an SR on this, too.


--
--------------------------------------------------------------------------
David Gersic dgersic_@_niu.edu
Knowledge Partner http://forums.netiq.com

Please post questions in the forums. No support provided via email.
If you find this post helpful, please click on the star below.
0 Likes
Anonymous_User Absent Member.
Absent Member.

Re: Google driver to handle new APIs?

On Wed, 08 Apr 2015 04:57:22 +0000, rdenys wrote:

> I believe I might be running into "Bug 924752" mentioned above, although
> I have an Organization setup, just no Sub-Organizations under that. I
> try and start the driver and receive the Null Pointer Exception error,
> the driver goes 'fatal' and wont start.
>
> However, as soon as I add a Sub-Organization, the driver starts fine.


You should open an SR on this.


--
--------------------------------------------------------------------------
David Gersic dgersic_@_niu.edu
Knowledge Partner http://forums.netiq.com

Please post questions in the forums. No support provided via email.
If you find this post helpful, please click on the star below.
0 Likes
Anonymous_User Absent Member.
Absent Member.

Re: Google driver to handle new APIs?


Hi David,

Cheers for the replies on this thread. I raised separate SR's for both
of the above issues. Turns out that an update to the Google Apps driver
was released on 09/04 which takes the driver now to version 4.0.5.0.
This newer version fixed the Null Pointer Exception thrown if no
sub-organization exists.

And yes, you are right about using "email". Using this attribute to
search on in the "Find Matching Object" token fixed my issue.

Just an FYI for others if they come across this thread, I was provided
the below link from NetIQ in regards to the changes between the Google
Provisioning API and the Google Directory API.

http://tinyurl.com/ovrkdj8

There are also alot of other links from this site off to the Admin SDK
regarding how the API handles HTTP requests and responses in JSON. I
found this to be terribly confusing, so try and stick with the link
above. Also, be aware that all calls to the Google Directory API are
case-sensitive. I got stuck for a while trying to write a mail NickName
to 'alias', whereas through the API 'Alias'. The confusing thing...
above where I use the Find Matching Object token, i search for 'email'
(lowercase).

It would be good to have the NetIQ developers document a mapping table
and have it in the driver documentation on their website. I guess that
might come in the near future.

Regards,
Ryan


--
rdenys
------------------------------------------------------------------------
rdenys's Profile: https://forums.netiq.com/member.php?userid=5605
View this thread: https://forums.netiq.com/showthread.php?t=51906

0 Likes
Anonymous_User Absent Member.
Absent Member.

Re: Google driver to handle new APIs?


Hey.

I found some lines from a BrainShare session I attended. I suspect this
is the content of DirectoryScopes.txt:
https://www.googleapis.com/auth/admin.directory.user
https://www.googleapis.com/auth/userinfo.email
https://www.googleapis.com/auth/userinfo.profile

Best Regards
Marcus


--
marcus_jonsson
------------------------------------------------------------------------
marcus_jonsson's Profile: https://forums.netiq.com/member.php?userid=1157
View this thread: https://forums.netiq.com/showthread.php?t=51906

0 Likes
Anonymous_User Absent Member.
Absent Member.

Re: Google driver to handle new APIs?


Daryl Creedy;255765 Wrote:
>
> When doing the steps in the PDF, it says to copy the contents of the
> DirectoryScopes.txt file. Where is that?
>
>
> Daryl


I am also looking for this information. It does not appear to be a file
included in the IDM45_GoogleApps_4040.zip file.

Mathieu


--
mdallaire
------------------------------------------------------------------------
mdallaire's Profile: https://forums.netiq.com/member.php?userid=3112
View this thread: https://forums.netiq.com/showthread.php?t=51906

0 Likes
Anonymous_User Absent Member.
Absent Member.

Re: Google driver to handle new APIs?

On Tue, 31 Mar 2015 12:54:01 +0000, mdallaire wrote:

> Daryl Creedy;255765 Wrote:
>>
>> When doing the steps in the PDF, it says to copy the contents of the
>> DirectoryScopes.txt file. Where is that?
>>
>>
>> Daryl

>
> I am also looking for this information. It does not appear to be a file
> included in the IDM45_GoogleApps_4040.zip file.


Yes. They're probably going to re-release the patch with the corrected
documentation.

Peter's message in this thread says that "DirectoryScopes.txt" most
likely contains:


SCOPE:
https://www.googleapis.com/auth/admin.directory.group,
https://www.googleapis.com/auth/admin.directory.group.member,
https://www.googleapis.com/auth/admin.directory.orgunit,
https://www.googleapis.com/auth/admin.directory.user,
https://www.googleapis.com/auth/admin.directory.user.alias,
https://www.googleapis.com/auth/admin.directory.user.security,
https://www.googleapis.com/auth/admin.directory.userschema,
https://www.googleapis.com/auth/userinfo.profile,
https://www.googleapis.com/auth/userinfo.email,
http://www.google.com/m8/feeds



--
--------------------------------------------------------------------------
David Gersic dgersic_@_niu.edu
Knowledge Partner http://forums.netiq.com

Please post questions in the forums. No support provided via email.
If you find this post helpful, please click on the star below.
0 Likes
Anonymous_User Absent Member.
Absent Member.

Re: Google driver to handle new APIs?

On Tue, 31 Mar 2015 12:54:01 +0000, mdallaire wrote:

> Daryl Creedy;255765 Wrote:
>>
>> When doing the steps in the PDF, it says to copy the contents of the
>> DirectoryScopes.txt file. Where is that?
>>
>>
>> Daryl

>
> I am also looking for this information. It does not appear to be a file
> included in the IDM45_GoogleApps_4040.zip file.


It looks like they re-released this as IDM45_GoogleApps_4040a.zip, which
now contains the setup documentation along with DirectoryScopes.txt.


--
--------------------------------------------------------------------------
David Gersic dgersic_@_niu.edu
Knowledge Partner http://forums.netiq.com

Please post questions in the forums. No support provided via email.
If you find this post helpful, please click on the star below.
0 Likes
Anonymous_User Absent Member.
Absent Member.

Re: Google driver to handle new APIs?


Perhaps I've missed something, but where is the "P12 Private Key File"
supposed to go? I've generated it, but I'm not sure where to place it
in the file system so the driver can read it to authenticate.


--
christb
------------------------------------------------------------------------
christb's Profile: https://forums.netiq.com/member.php?userid=6487
View this thread: https://forums.netiq.com/showthread.php?t=51906

0 Likes
Anonymous_User Absent Member.
Absent Member.

Re: Google driver to handle new APIs?

On 4/4/15 1:24 AM, christb wrote:
>
> Perhaps I've missed something, but where is the "P12 Private Key File"
> supposed to go? I've generated it, but I'm not sure where to place it
> in the file system so the driver can read it to authenticate.


The file should be somewhere on the file system where driver can read
it. /opt/novell/... is a good start.

I already asked them to update the documentation with this.


Casper


0 Likes
Anonymous_User Absent Member.
Absent Member.

Re: Google driver to handle new APIs?

On Fri, 03 Apr 2015 23:24:02 +0000, christb wrote:

> Perhaps I've missed something, but where is the "P12 Private Key File"
> supposed to go? I've generated it, but I'm not sure where to place it
> in the file system so the driver can read it to authenticate.


You specify the path and file name in the configuration, so you can put
it anywhere you want.


--
--------------------------------------------------------------------------
David Gersic dgersic_@_niu.edu
Knowledge Partner http://forums.netiq.com

Please post questions in the forums. No support provided via email.
If you find this post helpful, please click on the star below.
0 Likes
Anonymous_User Absent Member.
Absent Member.

Re: Google driver to handle new APIs?


Daryl Creedy;255765 Wrote:
> On 3/27/15 8:17 AM, Geoffrey Carman wrote:
> > On 3/27/2015 7:54 AM, ab wrote:
> >> Be sure you're pointing to a valid repository; Novell/NetIQ has used

> CDN
> >> for a while, and then that had issues, so now you should be pointed

> to
> >> nu.novell.com with the following (or so I think) URLs which should

> be
> >> present if you upgraded to Designer 4.5 SP0 Patch/AU 2 while in the
> >> current workspace (meaning if you've changed workspaces since then,

> you
> >> may need to copy the URLs over to that new workspace or else you're
> >> pointed to cdn.novell.com still which is not helpful to you

> anymore):
> >>
> >> https://nu.novell.com/designer/packages/idm/updatesite1_0_0/
> >> https://nu.novell.com/designer/packages/idm/updatesite2_0_0/
> >>
> >> Poking at these I see good things, even when not cheating and going

> to a
> >> local server, so hopefully that helps.

> >
> > The nu.novell.com for packages thing is new, and not announced

> anywhere
> > I have seen. I only knew about it because of a beta program using it.
> >
> > I see there at the end of the site.xml:
> >
> > <feature id="NOVLGGLEGRPS.feature"
> > url="features/NOVLGGLEGRPS.feature_2.0.2.20150127142148.jar"
> > version="2.0.2.20150127142148"/><feature id="NOVLGGLEBASE.feature"
> > url="features/NOVLGGLEBASE.feature_2.0.9.20150318214751.jar"
> > version="2.0.9.20150318214751"/><feature id="NOVLGGLEUSER.feature"
> > url="features/NOVLGGLEUSER.feature_2.0.4.20150218132136.jar"
> > version="2.0.4.20150218132136"/><feature id="NOVLGGLEBCFG.feature"
> > url="features/NOVLGGLEBCFG.feature_2.0.4.20150218131953.jar"
> > version="2.0.4.20150218131953"/>
> >
> > So there they are. PS: New stuff is always at the bottom of site.xml
> > unless they go out of their way to edit it by hand.)
> >
> >

> When doing the steps in the PDF, it says to copy the contents of the
> DirectoryScopes.txt file. Where is that?
>
>
> Daryl


Did you ever get an answer for this? I could not find it either.

Bruce


--
besposito
------------------------------------------------------------------------
besposito's Profile: https://forums.netiq.com/member.php?userid=2926
View this thread: https://forums.netiq.com/showthread.php?t=51906

0 Likes
Knowledge Partner
Knowledge Partner

Re: Google driver to handle new APIs?

On 4/1/2015 10:45 AM, besposito wrote:
>
> Daryl Creedy;255765 Wrote:
>> On 3/27/15 8:17 AM, Geoffrey Carman wrote:
>>> On 3/27/2015 7:54 AM, ab wrote:
>>>> Be sure you're pointing to a valid repository; Novell/NetIQ has used

>> CDN
>>>> for a while, and then that had issues, so now you should be pointed

>> to
>>>> nu.novell.com with the following (or so I think) URLs which should

>> be
>>>> present if you upgraded to Designer 4.5 SP0 Patch/AU 2 while in the
>>>> current workspace (meaning if you've changed workspaces since then,

>> you
>>>> may need to copy the URLs over to that new workspace or else you're
>>>> pointed to cdn.novell.com still which is not helpful to you

>> anymore):
>>>>
>>>> https://nu.novell.com/designer/packages/idm/updatesite1_0_0/
>>>> https://nu.novell.com/designer/packages/idm/updatesite2_0_0/
>>>>
>>>> Poking at these I see good things, even when not cheating and going

>> to a
>>>> local server, so hopefully that helps.
>>>
>>> The nu.novell.com for packages thing is new, and not announced

>> anywhere
>>> I have seen. I only knew about it because of a beta program using it.
>>>
>>> I see there at the end of the site.xml:
>>>
>>> <feature id="NOVLGGLEGRPS.feature"
>>> url="features/NOVLGGLEGRPS.feature_2.0.2.20150127142148.jar"
>>> version="2.0.2.20150127142148"/><feature id="NOVLGGLEBASE.feature"
>>> url="features/NOVLGGLEBASE.feature_2.0.9.20150318214751.jar"
>>> version="2.0.9.20150318214751"/><feature id="NOVLGGLEUSER.feature"
>>> url="features/NOVLGGLEUSER.feature_2.0.4.20150218132136.jar"
>>> version="2.0.4.20150218132136"/><feature id="NOVLGGLEBCFG.feature"
>>> url="features/NOVLGGLEBCFG.feature_2.0.4.20150218131953.jar"
>>> version="2.0.4.20150218131953"/>
>>>
>>> So there they are. PS: New stuff is always at the bottom of site.xml
>>> unless they go out of their way to edit it by hand.)
>>>
>>>

>> When doing the steps in the PDF, it says to copy the contents of the
>> DirectoryScopes.txt file. Where is that?
>>
>>
>> Daryl

>
> Did you ever get an answer for this? I could not find it either.


Still waiting on DirectoryScopes.txt but I notice that the nu.novell.com
URL now has 2 Trivir RSA driver packages (hopefully replacing the
deprecated 1.0 versions).

So that part has replicated my way at least.

Bottom items are:

<feature id="NOVLGGLEGRPS.feature"
url="features/NOVLGGLEGRPS.feature_2.0.2.20150127142148.jar"
version="2.0.2.20150127142148"/><feature id="NOVLGGLEBASE.feature"
url="features/NOVLGGLEBASE.feature_2.0.9.20150318214751.jar"
version="2.0.9.20150318214751"/><feature id="NOVLGGLEUSER.feature"
url="features/NOVLGGLEUSER.feature_2.0.4.20150218132136.jar"
version="2.0.4.20150218132136"/><feature id="NOVLGGLEBCFG.feature"
url="features/NOVLGGLEBCFG.feature_2.0.4.20150218131953.jar"
version="2.0.4.20150218131953"/><feature id="TRVRRSABASE.feature"
url="features/TRVRRSABASE.feature_1.0.2.20150317171209.jar"
version="1.0.2.20150317171209"/><feature id="TRVRRSADCFG.feature"
url="features/TRVRRSADCFG.feature_1.0.2.20150317171228.jar"
version="1.0.2.20150317171228"/>



0 Likes
Anonymous_User Absent Member.
Absent Member.

Re: Google driver to handle new APIs?

A related thread has a link to the updated patch stuff; copying here:

The DirectoryScopes.txt file is now available as a separate download for
those who have already downloaded the patch. It has also been included
in the patch zip file for those who have not already downloaded the
patch.
Patch link: https://dl.netiq.com/Download?buildid=buroXt9wsno~
Thread link: https://forums.netiq.com/showthread.php?t=53240


--
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: Google driver to handle new APIs?

On Wed, 25 Mar 2015 16:34:01 +0000, jbaylor1 wrote:

> It's been a month and I still haven't received notification that the new
> driver is ready.


It's out. You can download it now.


--
--------------------------------------------------------------------------
David Gersic dgersic_@_niu.edu
Knowledge Partner http://forums.netiq.com

Please post questions in the forums. No support provided via email.
If you find this post helpful, please 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.