We have moved to a new Sailfish OS Forum. Please start new discussions there.
1 | initial version | posted 2014-01-16 10:04:15 +0200 |
In addition to that ConnMan does not support certificate detail validation ConnMan also lacks the configuration settings for setting inner and outer EAP identity separately.
This means that the user is not able to set the outer identity in WiFi roaming networks to be for example anonymous@organisation.fi to protect user's true inner identity.
This also means that if organisation's authentication server is configured to accept only username without realm (e.g. user instead of user@organisation.fi), the user cannot configure ConnMan properly for roaming networks. This is because ConnMan seems to copy the inner identity to outer without possibility to add realm for WiFi roaming routing.
In addition to that ConnMan does not support certificate detail validation ConnMan also lacks the configuration settings for setting inner and outer EAP identity separately.
This means that the user is not able to set the outer identity in WiFi roaming networks to be for example anonymous@organisation.fi to protect user's true inner identity.
This also means that if organisation's authentication server is configured to accept only username without realm (e.g. user instead of user@organisation.fi), the user cannot configure ConnMan properly for roaming networks. This is because ConnMan seems to copy the inner identity to outer without possibility to add realm for WiFi roaming routing.