When choosing a CAT profile, the user is prompted for a password. The same also happens when the user sideloads a profile which requires username/password. The username/password screen doesn't contain information about the profile being installed.
Similarily, when side-loading a profile with client certificate, the app should show what it's about to install before it actually does so. And when asking for a PIN we should also see information about the institution.
The eap-config file can contain the name of the institution, a logo and contact information, so I was thinking we have three screens that can be presented to the user;
It should also be easier to implement the flow from Phase I correctly using these screens; the app works in two stages, stage 1 is to obtain
Here are some proposals for the screens that we would need.
(screen 1, no user info needed; user/pass or passphrase already provided)
<img LOGO>
<txt TITLE>
[btn Connect to network]
<link Support contact information>
(screen 2, username/password required)
<img LOGO>
<txt TITLE>
Username: [input]
Password: [input passphrase]
[btn Connect to network]
<txt (Note: if the connection fails, please check your password)>
<link Support contact information>
(screen 3, passphrase required, the passphrase should show as text and not as •••••)
<img LOGO>
<txt TITLE>
Passphrase: [input passphrase]
[btn Connect to network]
<link Support contact information>
When choosing a CAT profile, the user is prompted for a password. The same also happens when the user sideloads a profile which requires username/password. The username/password screen doesn't contain information about the profile being installed.
Similarily, when side-loading a profile with client certificate, the app should show what it's about to install before it actually does so. And when asking for a PIN we should also see information about the institution.
The eap-config file can contain the name of the institution, a logo and contact information, so I was thinking we have three screens that can be presented to the user;
It should also be easier to implement the flow from Phase I correctly using these screens; the app works in two stages, stage 1 is to obtain
Here are some proposals for the screens that we would need.
(screen 1, no user info needed; user/pass or passphrase already provided)
(screen 2, username/password required)
(screen 3, passphrase required, the passphrase should show as text and not as •••••)