Pete,
As you say, that looks fine…
But our 802.1X connections do not seem to use this cert, showing it as "Not
Verified"
The behavior that you are seeing saying “Not Verified”, is kind of the normal
behavior, as far as what we’ve seen. It is not an error, just the fact that the
cert is signed by a “third party chain” that is not “trusted” in the device
“cert store”.
That “Not Verified” message will show up only on first connection and when the
user accepts it, it will disapear.
I don’t know if anyone else on the list may have any other opinion ?
Derek
--
Derek Wuelfrath
[email protected] :: www.inverse.ca
+1.514.447.4918 (x110) :: +1.866.353.6153 (x110)
Inverse inc. :: Leaders behind SOGo (www.sogo.nu) and PacketFence
(www.packetfence.org)
On February 11, 2015 at 10:08:48, Pete Hoffswell ([email protected])
wrote:
Here's our eap.conf file. Looks pretty normal to me.
------------------------------------------------------------------------------
Dive into the World of Parallel Programming. The Go Parallel Website,
sponsored by Intel and developed in partnership with Slashdot Media, is your
hub for all things parallel software development, from weekly thought
leadership blogs to news, videos, case studies, tutorials and more. Take a
look and join the conversation now. http://goparallel.sourceforge.net/
_______________________________________________
PacketFence-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/packetfence-users
