User Authenticated Booking
iOS v4
Last updated
Was this helpful?
iOS v4
Last updated
Was this helpful?
It is highly recommended to first read the to get an an understanding of how booking functions in the MapsIndoors SDK.
By default, the MPBookingService performs anonymous bookings using a service account known to MapsIndoors. However, it is also possible to list, perform and cancel Bookings on behalf of a user. For the MPBookingService to work on behalf of a user, it must identify the tenant with a given tenant id (optional for single tenant setups) and prove user access with an access token. See the following example.
When the above configuration is in place, all following operations through the MPBookingService will be performed on behalf of a user. If the access token expires, the different Booking methods will result in errors and a new token must be obtained.
The tenant id is specific for each tenant / Booking provider. If you don't know your tenant id, your IT administrator should be able to provide the information needed. Note that this is optional for single tenant setups and single tenant setups are the most common.
Obtaining an access token for working with Bookings on behalf of a user is outside of the scope of this guide. Usually an access token is obtained in a login flow in your own application.
Note that the access token obtained from a cannot be used as access token for the
MPBookingService. Single Sign-on access tokens are issued by MapsIndoors and not the underlying tenant. You need to login directly on your Booking tenant to get an access token that can be used for working with the Booking Service as an authenticated user.
Disabling User Authenticated Bookings is as simple as setting the authenticationConfig to nil:
After disabling user authenticated Bookings, all following operations will be treated as anonymous Booking operations.