topic Re: VPN authentication OK, user authentication KO in General Topics

VPN authentication OK, user authentication KO

admincda — Fri, 17 Jun 2011 16:07:31 GMT

Hello

We have an active directory forest with 2 domains:

The first one as been configured in our PA2020 to allow VPN access through Radius and then we use AD groups to make policies rules.

All works fine. At login, users specify “username” and password without domain name.

Radius allows access and in PA2020 logs we can see user name: “domain1\username”

We need to add the second domain.

So we do the radius configuration, and then when user specify “domain2”\username the VPN login is allowed but the authentication transmit after radius login is wrong: “domain1\domain2\username”

We use a PA2020 cluster in 3.1.9.

How correct this?

Thanks in advance.

Re: VPN authentication OK, user authentication KO

pkruse — Tue, 28 Jun 2011 15:30:40 GMT

Are you using the same Radius server?

It sounds like the radius server is setup with the AD/Domain prefixed and when you use the second domain its prefixing the 1st domain to the second domain. Please contact support directly for assistance in setting up your authentication.

(8660 898-9087 or create a new case from your support portal.

Thank you,

Phil

Re: VPN authentication OK, user authentication KO

admincda — Tue, 28 Jun 2011 15:46:30 GMT

Hi thanks for answer.

Yes we use the same twin of radius server.

Yes it's exactly what's happen. But the it's a bugg for us, just a little verification on the CHAR if caracter "\" "or "@" is present, do not prefix username.
A case was opened yesterday by our support.

Thanks,

JHA

Re: VPN authentication OK, user authentication KO

admincda — Wed, 20 Jul 2011 15:54:15 GMT

Hi,

just an upgrade to 4.0.3 from 3.1.9 and all work fine.

I think that an issue was fixed without any report in release note.

bye,

JHA