Security

We have configured a guest portal where any guest can self-register using their phones as username. The behavior after expiration is "disable and logout" and we have also disabled the auto update field in the form, because we want that one phone only can register one account (with 3 devices allowed). The system shows an error message if the same phone try to register again.

In this scenario everything is working fine, however after expiration the same phone cannot create another account because it already exists in the accounts list. This is not real, because it exists but it is disabled (expired).

We know that we can change the behavior after expiration to "delete and logout", but we need to keep the list of old usernames. So, we have to avoid two phones registering twice during the account lifetime and we have to allow that this phone can create another account after expiration (disabled account).

We have configured a guest portal where any guest can self-register using their phones as username. The behavior after expiration is "disable and logout" and we have also disabled the auto update field in the form, because we want that one phone only can register one account (with 3 devices allowed). The system shows an error message if the same phone try to register again.

In this scenario everything is working fine, however after expiration the same phone cannot create another account because it already exists in the accounts list. This is not real, because it exists but it is disabled (expired).

We know that we can change the behavior after expiration to "delete and logout", but we need to keep the list of old usernames. So, we have to avoid two phones registering twice during the account lifetime and we have to allow that this phone can create another account after expiration (disabled account).

We have configured a guest portal where any guest can self-register using their phones as username. The behavior after expiration is "disable and logout" and we have also disabled the auto update field in the form, because we want that one phone only can register one account (with 3 devices allowed). The system shows an error message if the same phone try to register again.

In this scenario everything is working fine, however after expiration the same phone cannot create another account because it already exists in the accounts list. This is not real, because it exists but it is disabled (expired).

We know that we can change the behavior after expiration to "delete and logout", but we need to keep the list of old usernames. So, we have to avoid two phones registering twice during the account lifetime and we have to allow that this phone can create another account after expiration (disabled account).

We have configured a guest portal where any guest can self-register using their phones as username. The behavior after expiration is "disable and logout" and we have also disabled the auto update field in the form, because we want that one phone only can register one account (with 3 devices allowed). The system shows an error message if the same phone try to register again.

In this scenario everything is working fine, however after expiration the same phone cannot create another account because it already exists in the accounts list. This is not real, because it exists but it is disabled (expired).

We know that we can change the behavior after expiration to "delete and logout", but we need to keep the list of old usernames. So, we have to avoid two phones registering twice during the account lifetime and we have to allow that this phone can create another account after expiration (disabled account).

We have configured a guest portal where any guest can self-register using their phones as username. The behavior after expiration is "disable and logout" and we have also disabled the auto update field in the form, because we want that one phone only can register one account (with 3 devices allowed). The system shows an error message if the same phone try to register again.

In this scenario everything is working fine, however after expiration the same phone cannot create another account because it already exists in the accounts list. This is not real, because it exists but it is disabled (expired).

We know that we can change the behavior after expiration to "delete and logout", but we need to keep the list of old usernames. So, we have to avoid two phones registering twice during the account lifetime and we have to allow that this phone can create another account after expiration (disabled account).

We have configured a guest portal where any guest can self-register using their phones as username. The behavior after expiration is "disable and logout" and we have also disabled the auto update field in the form, because we want that one phone only can register one account (with 3 devices allowed). The system shows an error message if the same phone try to register again.

In this scenario everything is working fine, however after expiration the same phone cannot create another account because it already exists in the accounts list. This is not real, because it exists but it is disabled (expired).

We know that we can change the behavior after expiration to "delete and logout", but we need to keep the list of old usernames. So, we have to avoid two phones registering twice during the account lifetime and we have to allow that this phone can create another account after expiration (disabled account).

We have configured a guest portal where any guest can self-register using their phones as username. The behavior after expiration is "disable and logout" and we have also disabled the auto update field in the form, because we want that one phone only can register one account (with 3 devices allowed). The system shows an error message if the same phone try to register again.

In this scenario everything is working fine, however after expiration the same phone cannot create another account because it already exists in the accounts list. This is not real, because it exists but it is disabled (expired).

We know that we can change the behavior after expiration to "delete and logout", but we need to keep the list of old usernames. So, we have to avoid two phones registering twice during the account lifetime and we have to allow that this phone can create another account after expiration (disabled account).