On 11/26/2014 01:36 AM, Rolf Nufable wrote:
Actually the problem was that I was accessing our site from outside
our network now, our domain in the network locally is named
example.com, and the outside website is also at the domain example.com
so I guess what freeipa does is it looks for the website inside our
local network..
I looks for a name and DNS resolves it. So if DNS resolved to the
internal one then the internal will be used. If there is a route to the
external and DNS returned is then it will be external. It is really not
IPA's capability we are talking about here.
On Tuesday, November 25, 2014 10:32 PM, Outback Dingo
<[email protected]> wrote:
You probably want like a squid or oops proxy filter if you mean for
filtering web traffic.....
On Wed, Nov 26, 2014 at 4:51 PM, Fraser Tweedale <[email protected]
<mailto:[email protected]>> wrote:
On Wed, Nov 26, 2014 at 04:31:38AM +0000, Rolf Nufable wrote:
> Goodmorning
> Is there a function in freeipa that blocks websites?
Hi Rolf,
FreeIPA does not have this feature. It is a centralised identity
management system providing authentication and access control for
hosts and services managed by an organisation.
HTH,
Fraser
> --
> Manage your subscription for the Freeipa-users mailing list:
> https://www.redhat.com/mailman/listinfo/freeipa-users
> Go To http://freeipa.org <http://freeipa.org/> for more info on
the project
--
Manage your subscription for the Freeipa-users mailing list:
https://www.redhat.com/mailman/listinfo/freeipa-users
Go To http://freeipa.org <http://freeipa.org/> for more info on
the project
--
Thank you,
Dmitri Pal
Sr. Engineering Manager IdM portfolio
Red Hat, Inc.
--
Manage your subscription for the Freeipa-users mailing list:
https://www.redhat.com/mailman/listinfo/freeipa-users
Go To http://freeipa.org for more info on the project
