HSNM DOUBTS
Posted: 04 May 2024, 17:29
Hello, I am going to ask you several questions:
Let's imagine that I have an API (from a PMS) that creates users in the HSNM when the guest checks in. PMS attacks HSNM and creates the user as follows:
Username: email provided by the guest at check-in.
Password: First or Last Name (I would prefer it to be the room, but you only have this option for usernames).
1) The password has a minimum of 4 characters, but there are people with first and last names of 3 characters, what would happen in this case?
Let's imagine that the user has an expired product and is going to extend his stay by 3 more days or returns to the hotel the following year.
2) What happens in this case?
Option A: PMS recreates the same user by overwriting it?
Option B: PMS can do the recharge via API?.
I understand that overwriting it is not advisable because traceability is lost.
What do you usually do in these cases? The idea is to automate everything from the PMS (without using vouchers for renewals).
3) In the option you have that the user name is the room (PMS), how do you keep the user data in the database? Rooms (usernames) are supposed to be constantly reused. How does user creation behave in this case? Are users who stay in the same rooms overwriting all the time?
4) Can products of already created users be updated from the API?
5) Technically (ports, configurations), in the HSNM do I need for the PMS to attack the HSNM via API?
Thank you so much.
Let's imagine that I have an API (from a PMS) that creates users in the HSNM when the guest checks in. PMS attacks HSNM and creates the user as follows:
Username: email provided by the guest at check-in.
Password: First or Last Name (I would prefer it to be the room, but you only have this option for usernames).
1) The password has a minimum of 4 characters, but there are people with first and last names of 3 characters, what would happen in this case?
Let's imagine that the user has an expired product and is going to extend his stay by 3 more days or returns to the hotel the following year.
2) What happens in this case?
Option A: PMS recreates the same user by overwriting it?
Option B: PMS can do the recharge via API?.
I understand that overwriting it is not advisable because traceability is lost.
What do you usually do in these cases? The idea is to automate everything from the PMS (without using vouchers for renewals).
3) In the option you have that the user name is the room (PMS), how do you keep the user data in the database? Rooms (usernames) are supposed to be constantly reused. How does user creation behave in this case? Are users who stay in the same rooms overwriting all the time?
4) Can products of already created users be updated from the API?
5) Technically (ports, configurations), in the HSNM do I need for the PMS to attack the HSNM via API?
Thank you so much.