Authentication
Overview
When an SMPP endpoint within the SMPP application receives a bind request of any form the endpoint will:
- Respond with a success response if no
authentication-address
has been configured. - Otherwise send an authentication request to the configured
authentication-address
application.
When requesting authentication, the authentication request will include:
- The bind message’s SMPP
System ID
as the authentication request username. - The bind message’s SMPP
Password
as the authentication request password. - The bind message’s SMPP
System Type
as the authentication request service.
If the authentication response from the JSLEE authentication application indicates a successful login, the SMPP
endpoint will respond to the bind request with success. Otherwise the SMPP failure code ESME_RBINDFAIL
will be sent back to the remote endpoint.
Authentication Grants
Groups
The following authentication groups are relevant to SMPP authentication:
Group | Use |
---|---|
RX |
Indicates that the service account can connect using a bind_receiver request. |
TX |
Indicates that the service account can connect using a bind_transmitter request. |
TRX |
Indicates that the service account can connect using a bind_transceiver request. |
Group configuration may immediately invalidate a successful authentication if the SMPP bind request was performed using a bind type that is not authorized.
If none of the groups listed above are included in the authentication configuration, then any bind type will be allowed. This means that an authentication configuration for a SMPP connection may either list all bind types as groups, or none - both approaches provide the same functionality. Listing at least one, but fewer than all bind types will define a restriction.
Attributes
No authentication attributes are used by the SMPP service.