dstucke Absent Member.
Absent Member.
1007 views

Can Filr be used for (edir) authenticated file sharing

We want to share some docs with other organisations over the internet, like an FTP server but with Filr.
Can Filr be used for (edir) authenticated file sharing? I suppose so, but what are the licensing implications for an OES network?
Would every remote non-inhouse user with a logon need a full OES license, or is there some sort of public licensing?
0 Likes
1 Reply
jmarton2 Absent Member.
Absent Member.

Re: Can Filr be used for (edir) authenticated file sharing

dstucke wrote:

>
> We want to share some docs with other organisations over the internet,
> like an FTP server but with Filr.
> Can Filr be used for (edir) authenticated file sharing? I suppose so,
> but what are the licensing implications for an OES network?
> Would every remote non-inhouse user with a logon need a full OES
> license, or is there some sort of public licensing?


1)
If you want eDir authenticated file sharing leveraging OES storage
you'd have to create additional OES users which would mean purchasing
additional OES licenses.


2)
Now if you wanted, you could create a separate eDir tree for external
users and point Filr to that tree as a separate LDAP source. After
all, your OES licensing entitles you 250k users of eDir for any sort of
use. Just keep in mind if you do this, those users would not have
access to resources on your OES servers in your production tree. All
you could do would be to leverage personal storage which would be
storage on the appliance. This would also require purchasing
additional Filr licenses (less costly than purchasing additional OES
licenses).

3)
You also have the option to create local Filr users. These are users
who don't exist within any LDAP source. The same caveats as #2 would
exist as far as the storage these users could access. This would also
require additional Filr licenses.

One thing to keep in mind about #2 or #3 is that your regular internal
Filr users can still share files and even folders with users in a
separate tree or local Filr users. In this scenario those "external"
users (for lack of a better term) would be able to access OES resources
using the rights of the proxy user defined in the properties of the NF
Server.

There's one last thing to keep in mind. As a user I can share with
some externally and that doesn't require any additiona licensing.
That's one of the great things about Filr. The only time you need
additional licenses is when as the administrator you define additional
Filr users who aren't otherwise covered by the free entitlement from
OES.

--
Your world is on the move. http://www.novell.com/mobility/
We know what your world looks like. http://www.novell.com/yourworld/

Joe Marton Emeritus Knowledge Partner
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.