- Community Home
- >
- Networking
- >
- IMC
- >
- Re: 802.1x on IMC UAM
Categories
Company
Local Language
Forums
Discussions
Forums
- Data Protection and Retention
- Entry Storage Systems
- Legacy
- Midrange and Enterprise Storage
- Storage Networking
- HPE Nimble Storage
Discussions
Discussions
Discussions
Forums
Discussions
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
- BladeSystem Infrastructure and Application Solutions
- Appliance Servers
- Alpha Servers
- BackOffice Products
- Internet Products
- HPE 9000 and HPE e3000 Servers
- Networking
- Netservers
- Secure OS Software for Linux
- Server Management (Insight Manager 7)
- Windows Server 2003
- Operating System - Tru64 Unix
- ProLiant Deployment and Provisioning
- Linux-Based Community / Regional
- Microsoft System Center Integration
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Community
Resources
Forums
Blogs
- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark
- Subscribe
- Printer Friendly Page
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
03-25-2013 07:37 AM
03-25-2013 07:37 AM
Two questions:
1) Is possible to configure simple 802.1x without use of certificate?
2) Is possible to configure simple 802.1x (no certificate) without iNode? Use iNode would force users to install the tool on client PC and many customers don't want it.
Anyone confirm this two point?
FB
Solved! Go to Solution.
- Tags:
- certificate
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
03-28-2013 02:18 PM
03-28-2013 02:18 PM
SolutionHi,
1/ The whole point of 802.1x is to have secure auth. You should be using a cert on the radius server (can be self-signed or generated by the internal CA) for the secure 802.1x auth options.
IMC UAM would also support EAP-MD5 (which does not require cert on UAM), but this is not recommended (and e.g. Microsoft supplicant does not even support this, which is a good thing).
2/ Once you get over the fact you need the cert, UAM support EAP-PEAP-MSchapv2 or EAP-TLS (client cert based). For the EAP-PEAP-MSchapv2 method, the built-in Microsoft supplicant can be used for the authentication.
Best regards,Peter.
- Tags:
- 802.1x on IMC
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
03-31-2013 03:29 AM
03-31-2013 03:29 AM
Re: 802.1x on IMC UAM
Peter, thank you very much!
I know that the use of the certificate is more suitable but I was willing to work, initially, a 802.1x authentication mechanism in the simplest way.
I'll try both ways in the hope of not encounter difficulties.
So as I understand EAP-TLS would force me to use iNode?
Well, then I'll try to choose EAP-PEAP.
Thanks a lot for the solution.
FB
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
04-02-2013 01:02 PM
04-02-2013 01:02 PM
Re: 802.1x on IMC UAM
Hi,
EAP-TLS means you need a certificate on the client side. This is independent of the client suplicant (windows or iNode), so a lot of companies find managing the client certificates too complex and do not consider the EAP-TLS method.
So if you want to use EAP-TLS with UAM, the windows suplicant can be used as well,
Best regards,Peter.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
04-04-2013 08:34 AM
04-04-2013 08:34 AM
Re: 802.1x on IMC UAM
Tnx.
Well, I try to configure 802.1x with IMC and wireless MSM.
I have:
1) on IMC: configured access device (access controller MSM760)
2) on IMC: created a service (called wir_serv) with Certificate Authentication: None (is correct this?!?)
3) on IMC: created a user with access service wir_serv
4) on MSM: created a SSID with 802.1x WPA2 and remote RADIUS Authentication
but when i try to connect with user, on log management, i can view the log of authentication tentative.
the result is: E63001::Process failed
what mean "E63001::Process failed".
is always NOT possible configure a 802.1x with MSM without use of certificate?!?
FB
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
04-05-2013 02:14 AM
04-05-2013 02:14 AM
Re: 802.1x on IMC UAM
Hi,
Which client supplicant are you using ?
* Since you have not installed a cert on the UAM server, it means you will be using MD5 (not recommended !), which is even not supported e.g. the default Windows supplicant.
So if you really want this unsecure method, you need to install 3th party supplicant software (opensource or iNode client).
* For proper testing, install a cert (any will do, can be selfsigned) on the UAM server first, next you can use the PEAP-MSCHAPv2 method to login with username+password.
Best regards,Peter
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
04-06-2013 12:33 AM
04-06-2013 12:33 AM
Re: 802.1x on IMC UAM
Hi Peter,
at the end I managed to run 802.1x with IMC and a MSM controller.
It was hard, very hard.
Yes, the problem was that I had not imported the certificate on IMC... the most obvious thing.
Now all work correctly and the client authenticates only with username and password (I used PEAP and TLS).
Finally!
Thank you very much for your answers! You've been very helpful... Thank you.
FB