Highlighted
Absent Member.
Absent Member.
261 views

O355 driver refresh application schema - is this supported?

I have an O365 driver (patched to 4.5.2 + shim 4.1.0.2.

The driver works and can provision users fine.

I tried to "refresh app schema" via Designer.

Driver shut down with an error.

Shouldn't this be supported, it is a standard driver feature!
Labels (1)
0 Likes
6 Replies
Highlighted
Knowledge Partner
Knowledge Partner

Re: O355 driver refresh application schema - is this support

It is if the application supports it.

Could only find that Geoffry coudn't do it either:
I asked some NetIQ contacts if the driver supports getSchema() and if so, to get me the DirXML-ApplicationSchema attribute from the driver. If your driver supports getSchema() then on the first driver start, and anytime you Refresh Application Schema in iManager, the driver calls the getSchema() function, which is supposed to return the entire application schema and store it on the driver object as DirXML-ApplicationSchema. Not all drivers support it (often the application may not provide it, in which case, the basic driver configuration could pre-populate the attribute, or just ignore it altogether).

From https://www.netiq.com/communities/cool-solutions/walking-through-the-office-365-idm-driver-part-3/


Ohh, there is a tid about the problem: https://www.netiq.com/support/kb/doc.php?id=7016270


0 Likes
Highlighted
Absent Member.
Absent Member.

Re: O355 driver refresh application schema - is this supported?

joakim ganse wrote:

>
> It is if the application supports it.
>
> Could only find that Geoffry coudn't do it either:


There is a DirXML-ApplicationSchema attribute present, but not yet
checked when it was last updated.

I know that at least one attribute (AlternateEmailAddresses) in that
schema is incorrectly quoted as multi-valued but when you try and treat
it as such, shim returns an error. Wondering if there are more.


> there is a tid about the problem:
> 'https://www.netiq.com/support/kb/doc.php?id=7016270


I saw that, but I'm doing everything as per the TID.
Running remote, as a service and have the right patches / dependancies
installed.

The driver does startup.
0 Likes
Highlighted
Knowledge Partner
Knowledge Partner

Re: O355 driver refresh application schema - is this supported?


Hi Alex,
Do you have "your" O365 Application schema visible in your Designer?


--
If you find this post helpful, please show your appreciation by clicking
on the star below :cool:
------------------------------------------------------------------------
al_b's Profile: https://forums.netiq.com/member.php?userid=209
View this thread: https://forums.netiq.com/showthread.php?t=55830

0 Likes
Highlighted
Knowledge Partner
Knowledge Partner

Re: O355 driver refresh application schema - is this supported?

al b <al_b@no-mx.forums.microfocus.com> wrote:
>

Hi Alex,
> Do you have "your" O365 Application schema visible in your Designer?


Nope


--
If you find this post helpful and are logged into the web interface, show
your appreciation and click on the star below...
Alex McHugh - Knowledge Partner - Stavanger, Norway
Who are the Knowledge Partners
If you appreciate my comments, please click the Like button.
If I have resolved your issue, please click the Accept as Solution button.
0 Likes
Highlighted
Knowledge Partner
Knowledge Partner

Re: O355 driver refresh application schema - is this supported?


alexmchugh;267566 Wrote:
> al b <al_b@no-mx.forums.microfocus.com> wrote:
> >

> Hi Alex,
> > Do you have "your" O365 Application schema visible in your Designer?

>
> Nope
>
>
> --
> If you find this post helpful and are logged into the web interface,
> show
> your appreciation and click on the star below...


Currently I can't confirm (or decline it), but it also can be issue with
..Net Remote Loader schema refresh functionality: when you try to
"refresh" App schema (even when you have driver started), it tried to
close connection (that take a long-long time...) and start the
connection again...
In 99.99% you will get "timeout" error instead app schema refresh.

Alex


--
If you find this post helpful, please show your appreciation by clicking
on the star below :cool:
------------------------------------------------------------------------
al_b's Profile: https://forums.netiq.com/member.php?userid=209
View this thread: https://forums.netiq.com/showthread.php?t=55830

0 Likes
Highlighted
Knowledge Partner
Knowledge Partner

Re: O355 driver refresh application schema - is this supported?

al b <al_b@no-mx.forums.microfocus.com> wrote:
>
> Currently I can't confirm (or decline it), but it also can be issue with

...Net Remote Loader schema refresh functionality: when you try to
"refresh" App schema (even when you have driver started), it tried to
close connection (that take a long-long time...) and start the
connection again...
> In 99.99% you will get "timeout" error instead app schema refresh.
>


Interesting that needs to be tested!!

--
If you find this post helpful, please show your appreciation by clicking
on the star below :cool:
------------------------------------------------------------------------
al_b's Profile: https://forums.netiq.com/member.php?userid=209
View this thread: https://forums.netiq.com/showthread.php?t=55830

>




--
If you find this post helpful and are logged into the web interface, show
your appreciation and click on the star below...

Alex McHugh - Knowledge Partner - Stavanger, Norway
Who are the Knowledge Partners
If you appreciate my comments, please click the Like button.
If I have resolved your issue, please click the Accept as Solution button.
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.