fuzziebrain Absent Member.
Absent Member.
2707 views

Novell Access Manager Integration

I have looked at the documentations for both Vibe 3.2 and Add-in, but did not find any information on how to configure Novell Access Manager (NAM) for Vibe Add-in. Maybe I missed something. I do understand that the product is still in Beta, so any guidance on configuring NAM to support Vibe Add-in (and Desktop) would be deeply appreciated.

Thanks and best regards,
Adrian
Labels (1)
0 Likes
4 Replies
Anonymous_User Absent Member.
Absent Member.

Re: Novell Access Manager Integration

fuzziebrain,

It appears that in the past few days you have not received a response to your
posting. That concerns us, and has triggered this automated reply.

Has your problem been resolved? If not, you might try one of the following options:

- Visit http://support.novell.com and search the knowledgebase and/or check all
the other self support options and support programs available.
- You could also try posting your message again. Make sure it is posted in the
correct newsgroup. (http://forums.novell.com)

Be sure to read the forum FAQ about what to expect in the way of responses:
http://forums.novell.com/faq.php

If this is a reply to a duplicate posting, please ignore and accept our apologies
and rest assured we will issue a stern reprimand to our posting bot.

Good luck!

Your Novell Product Support Forums Team
http://forums.novell.com/

0 Likes
bramsey Absent Member.
Absent Member.

Re: Novell Access Manager Integration

Hi,
although I'll admit I haven't looked at the details of the add-in, I think we use webservices, webdav and standard ports (8443 is in the docs) for office add-in. The NAM configuration will be the same since we already have to configure the proxy to access these services. I know there is some discussion of additional protected resources for the Webapp/NAM, but not any I know of for the office add-in. Are you having any problems with it?
0 Likes
fuzziebrain Absent Member.
Absent Member.

Re: Novell Access Manager Integration

bramsey;2182664 wrote:
Hi,
although I'll admit I haven't looked at the details of the add-in, I think we use webservices, webdav and standard ports (8443 is in the docs) for office add-in. The NAM configuration will be the same since we already have to configure the proxy to access these services. I know there is some discussion of additional protected resources for the Webapp/NAM, but not any I know of for the office add-in. Are you having any problems with it?


Hi Bramsey,

Sorry for my late reply. The solution provided by ksiddiqui in this thread worked for me. Any issues with either the three: mobile apps, add-in and desktop, would be fixed at one go. If you haven't, you might want to give that a try.

Best regards,
Adrian
0 Likes
David_Main Absent Member.
Absent Member.

Re: Novell Access Manager Integration

Hi, we had the same issue and resolved it with the following:

For the Authentication Procedure, select the procedure you just created.
In the URL Path List, remove the /* path and add the following paths:

/ssfs/*
/ssf/atom/*
/ssf/ical/*
/ssf/ws/*
/ssf/rss/*
/ssr/*
/rest/*

The /ssfs/* path is for WebDAV content and the /ssf/rss/* path enables non-redirected login for RSS reader connections. Vibe provides authentication for all of the paths listed above.

Click OK.

/ssf/a/c/p_name/ss_mobile/*


Current config that does not work:
Paths Close
/ssf/atom/*
/ssf/ical/*
/ssf/rss/*
/ssfs/*

NEW config that does work

/ssf/atom/*
/ssf/ical/*
/ssf/rss/*
/ssfs/*
/ssf/ws/*
/ssr/*
/rest/*
/ssf/a/c/p_name/ss_mobile/*

Hope this helps others
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.