EFW Support

Support => EFW SMTP, HTTP, SIP, FTP Proxy Support => Topic started by: davevo on Thursday 17 July 2014, 12:01:09 am



Title: Endian 3.0 proxy access policy not working?
Post by: davevo on Thursday 17 July 2014, 12:01:09 am
Hi all,

Like my previous thread, I've upgraded from Endian 2.5.1 to 3.0 and now the access policies don't work.

On 2.5.1 - I had it authenticating with AD - working perfectly fine.
On 3.0 - I have it authenticated with AD and joined the domain. I can see users fine, but I can't get policies to work with them. Nor can I get a blanket cover policy without user authentication (ie: user - disabled). It will still allow pages to through, even though I've blanket covered them in the profile and denied them in the access policy.

Any thoughts?


Title: Re: Endian 3.0 proxy access policy not working?
Post by: kevinb on Tuesday 22 July 2014, 06:19:20 am
I too am having trouble but in a different sense.

I have authentication configured against a LDAP server. I can see the uses and groups in the EFW pull down menus.

However when a user is prompted for a name and password the page is always denied.

Is there a bug in the code that performs the authentication?

Where can I look to find any any info? The logs are pretty bare about this.

Thanks,

Kevin


Title: Re: Endian 3.0 proxy access policy not working?
Post by: Di4bLo on Sunday 24 August 2014, 08:07:41 am
Same problem kevinb.
With authentication I can't see any website: access denied.


Title: Re: Endian 3.0 proxy access policy not working?
Post by: Di4bLo on Friday 05 September 2014, 05:30:35 pm
After some changes now works well with Internet Explorer 11 and Windows 7, not on FF or Chrome.
It's soooooo weird.



Title: Re: Endian 3.0 proxy access policy not working?
Post by: kevinb on Tuesday 09 September 2014, 05:29:37 am
What changes Di4bLo?


Title: Re: Endian 3.0 proxy access policy not working?
Post by: Di4bLo on Monday 29 September 2014, 06:39:11 pm
Unfortunately I can't tell you mate.
I was following up some procedures to try to fix the problem and I realize it was working on IE11.
Now it seems that it works only if clients are joined to the domain.
I can't understand why it doesn't work and more than this I can't believe nobody can fix it (considering it was good on the previous version).

 ??? ??? ??? ??? ???