1. Authentication Center for SDP Federation
Motorola Israel Project:
Authentication Center for SDP Federation
Prototype Presentation
The Team:
Alina Mirinzon
Gabi Brontvin
Raz Zieber
Dadi Suissa

2. System Architecture
Legend:

3. Prototype Network Authentication: Authentication process –
EAP-MD5 state machine & GUI
SDP Authentication server stub – (DIAMETER server)
Protocols conversion (RADIUS DIAMETER)
Xsupplicant (access request)
Sniffer

4. Prototype SDP Authentication : Authentication process –
part of state machine & GUI
SDP authentication server stub – (DIAMETER server)
Parlay interfaces implementation (partial)
Application (service request & GUI)
Service stub
RMI communication (server & client)

5. SDP Authentication Sequence
Application
Authentication
Center
Select Hash Algorithm
Challenge
Challenge Response
Authenticate AC with Challenge Response
Authentication AC succeed
Handshake
Challenge
Challenge Response
Authenticate Application with Challenge Response
Authentication Application succeed

6. SDP Authentication Sequence
Servers
Application
Authentication
Center
Request IpAccess
IpAccess
Register to services
Loop
Authentication Process
Authenticate each requested service
Authentication answer for each requested service
Final authentication answer
SDP Services
Provider Servers
If (Final authentication answer = true)
Use services

7. Network Authentication

8. Network Authentication
EAPOL Frame Format :
Packet type field :
EAP Packet 1
EAPOL Start 2
EAPOL Logoff 3
EAPOL Key 4
EAPOL Encapsulated ASF Alert

9. Network Authentication
EAP Packet Format :
EAP code types :
EAP authentication types : 1
Request 2
Response 3
Success 4
Fail 1
Identity 2
Notification 3
Nak (response only) 4
MD5-Challenge 5
One-Time Password 6
Generic Token Card
The ID is one byte for matching requests
and responses. Length is the byte count
including the code, ID, length and data fields.
The data field format varies depending on the code field. Types 3 and 4, Success and Failure
are easy to describe: they have no data field (0 bytes). Types 1 and 2 share a format.

10. Next Steps… DIAMETER server & client –
establishment, configure & integration
Continue protocol conversion –
according to DIAMETER server
Continue Parlay interfaces implementation
Certificate Authority development
Building repository
Testing plan documents
User manual
Final system delivery tests
Integration at costumer site

11. Authentication Center for SDP Federation
Thank You !