Every user needs to authenticate with QuickBlox before using any QuickBlox functionality. When someone connects with an application using QuickBlox, the application will need to obtain a session token which provides temporary secure access to QuickBlox APIs. A session token is an opaque string that identifies a user and an application. Visit Key Concepts page to learn the most important QuickBlox concepts.

​
Before you begin

  1. Register a QuickBlox account. This is a matter of a few minutes and you will be able to use this account to build your apps.
  2. Configure QuickBlox SDK for your app. Check out Setup page for more details.

​
Session token rights

There are different types of session tokens to support different use cases.
Session Token TypeDescription
Application session tokenThis kind of access token is needed to read the app data. Has only READ access to resources. The expiration time after the last REST API request is 2 hours.
User session tokenThe user token is the most commonly used type of token. This kind of access token is needed any time the app calls an API to read, modify or write a specific user’s data on their behalf. Has READ/WRITE access to resources. The expiration time after the last REST API request is 2 hours.

​
Session management

By default, when a session gets expired, a new session with a new session token is created automatically. Thus, QuickBlox SDK stores a session token and uses it for all subsequent requests within the current session.

​
Get session

At any time you can get details about your current session. 
QBSession.current.sessionDetails

​
Sign up user

Before you log in the user, you must create the user on QuickBlox. Recommendations are below:
  1. For POCs/MVPs: Create the user using the QuickBlox Dashboard or in client app with application session token.
  2. For production apps: Use the QuickBlox Create User API with API key on your backend to create the user when your user signs up in your app.
SecurityIt’s recommended to disable permission to create users with application session on production apps once user creation is implemented on your backend.
You can create a user with application session token in client app by calling signUp() method. 
let userInfo = QBUUser()
userInfo.login = "myLogin"
userInfo.fullName = "myFullName"
userInfo.password = "myPassword"

let user = try await QBRequest.signUp(userInfo)

​
Log in user

QuickBlox provides four types of user authentication: login/email and password, social, phone number, and custom identity provider login.

​
Login/email and password

Log in a user just by using login (or email) and password. Other fields are optional. Thus, the QuickBlox server requests a users database for a match. If there is a match, a user session is created. 
let user = try await QBRequest.login("userLogin", password: "userPassword")

​
Social

Authenticate with QuickBlox using a social network access token. 
let socialProvider = "facebook"
let accessToken = "Az9dgLfyK7tZBSAz9dgLfyK7tQNttIoaZA10niR68DO" //Social provider's access token.

QBRequest.logIn(withSocialProvider: socialProvider, accessToken: socialProviderAccessToken, accessTokenSecret: nil, successBlock: { (response, user) in
    //Block with response and user instances if the request is succeeded.
}, errorBlock: { (response) in
    //Block with response instance if the request is failed.
})
ParametersDescription
socialProviderA social network provider.
accessTokenAn access token received from the social network after a user authenticates with it.
accessTokenSecretA social network provider’s access token secret.

​
Phone number

A sign-in with a phone number is supported with Firebase integration. In order to implement authentication via phone number functionality, follow this Firebase document. Don’t forget to enable phone number sign-in for your Firebase project. To learn how to do this, see this Firebase document. Send a verification code to the user’s phone and sign in the user on Firebase with the received verification code. Then, log in the user to QuickBlox. To log in the user, use the logIn() method. Pass the project ID and ID token to the logIn() method. The ID token is received as a result of getIdToken() method. 
import Firebase
import FirebaseUI

private func performPhoneLogin() {
    guard let authUI = FUIAuth.defaultAuthUI() else {
        return
    }
    authUI.delegate = self
    let phoneAuth = FUIPhoneAuth(authUI: authUI)
    authUI.providers = [phoneAuth]
    phoneAuth.signIn(withPresenting: self, phoneNumber: nil)
}

//MARK: - FUIAuthDelegate
extension AuthViewController: FUIAuthDelegate {
    func authUI(_ authUI: FUIAuth, didSignInWith authDataResult: AuthDataResult?, error: Error?) {
        if error != nil {
            return
        }
        guard let authDataResult = authDataResult else {
            return
        }

        let myFirebaseprojectID = "thisIsProjectIDFromFirebase" //Firebase project ID

        authDataResult.user.getIDToken(completion: { (token, completionError) in
            guard let token = token else {
                return
            }
            QBRequest.logIn(withFirebaseProjectID: myFirebaseprojectID, accessToken: token, successBlock: { (response, user) in
                //Block with response and user instances if the request is succeeded.
            }) { (response) in
                //Block with response instance if the request is failed.
            }
        })
    }
}
Pass the following arguments to the logIn() method.
ArgumentsDescription
myFirebaseprojectIDFirebase project ID. When you create a Firebase project, Firebase automatically assigns a unique ID to the project, but you can edit it during the project setup.
tokenID token of the Firebase user. Created by Firebase when a user signs in to an app. This token is received as a result of getIdToken() method.

​
Custom identity provider

You can authenticate your application users from the external database with QuickBlox via Custom Identity Provider (CIdP). Just specify the user login and access token as a password to authenticate with QuickBlox. Review Custom Identity Provider page for more details on the feature. 
let externalUserLogin = "myQBLogin" //External backend user ID. Posible values: externalUser.ID, externalUser.phoneNumber, externalUser.email, or any other field you would like to use as a unique identifier.
let externalUserPassword = "Fd4kxd37z58dS4d2Ye7wh3" //Token received by the user during authentication on the external backend

QBRequest.logIn(withUserLogin: externalUserLogin, password: externalUserPassword, successBlock: { (response, user) in
    //Block with response and user instances if the request is succeeded.
}, errorBlock: { (response) in
    //Block with response instance if the request is failed.
})
This feature is available for customers on the Enterprise plan only. Take advantage of Enterprise features to unlock new value and opportunities for users. For more information and if you want to request a Demo, please contact us by mail: enterprise@quickblox.com.

​
Log out user

If you have a user session, you can downgrade it to an application session by calling logout() method. 
try await QBRequest.logOut()

​
Destroy session token

To destroy a session, use the following code. 
QBRequest.destroySession(successBlock: { (response) in

}, errorBlock: { (response) in

})

​
Set existing session

Typically, a session token is stored in SDK after successful login and used for every subsequent API call. However, you may want to obtain and store the session on your server for better security. In this case, you can set the existing session token into SDK using the startSession(withToken:) method. It’s can be application or user token. Don’t forget to log in user if you pass the application token. 
QBSessionManager.instance.startSession(withToken:"f23d03bd2341a1f923b7d4c1fbee97af1cd296f2")
Use QBSessionManagerDelegate to handle session life cycle. 
class YourClass: NSObject {
    override init() {
        super.init()
        QBSessionManager.instance.addDelegate(self)
    }
}

extension YourClass: QBSessionManagerDelegate {
    func sessionManager(_ manager: QBSessionManager, didStartSessionWithDetails details: QBASession) {
    }

    func sessionManager(_ manager: QBSessionManager, didNotStartSessionWithError error: Error?) {
    }

    func sessionManagerDidExpireSession(_ manager: QBSessionManager) {
    }
}
If you have version lower than 2.8.0, use QBSession class to set the existing session token
let sessionDetails = QBASession()
sessionDetails.token = "f23d03bd2341a1f923b7d4c1fbee97af1cd296f2"

// updateSessionBlock executes synchronously on background thread and you are allowed to execute synchronous URL request
// and to block a background thread from executing until you receive updated credentials
// by the end of updateSessionBlock you should call startSessionWithDetails: with updated credentials

QBSession.current.start(withDetails: sessionDetails, updateSessionBlock: {
    // Execute synchronous URL request to retrieve new token from custom server
    // Until the end of this block all the operations will be paused
    let updatedSessionDetails = QBASession()
    updatedSessionDetails.token = "new token"//new token from custom server
    // Start Updated Session
    QBSession.current.start(withDetails: updatedSessionDetails)
})