Abstract:
A user device stores first authentication information used to grant access to a resource associated with a first application, and configuration information relating to a second application. The user device receives an authentication request from the second application requesting second authentication information. Based on the configuration information relating to the second application, the user device determines whether the first authentication information contains some or all of the requested second authentication information. The user device generates an authentication response to the authentication request, using the first authentication information, and sends the authentication response to the second application in order to permit access to a resource associated with the second application.
Abstract:
The device may receive user information associated with a user. The device may generate a user profile for the user that stores user information and authentication confirmation information. The device may provide a particular cryptographic key and information identifying the user profile. The device may receive a request to authenticate a secure session for a user device from an application server. The device may obtain, based on the user identifier, the authentication confirmation information associated with the user from a data structure storing one or more user profiles. The device may validate the particular response to the particular challenge code based on the authentication confirmation information. The device may provide information to the application server indicating that the secure session is validated for the user device based on validating the authentication information.
Abstract:
An authentication device may provide an authentication code to a third party device. The third party device may provide a third party service to which a client device has requested access. The authentication device may receive the authentication code from a mobile device that is different from the client device. The authentication device may determine a third party device identifier included in the authentication code. The third party device identifier may identify the third party device that provides the third party service. The authentication device may determine a transaction identifier included in the authentication code. The authentication device may selectively provide the transaction identifier to the third party device, identified by the third party device identifier, to cause the third party device to selectively permit the client device to access the third party service.
Abstract:
A device may receive an indication to generate a link associated with accessing a message. The message may be intended for a shared device identifier of a receiver device identified by a receiver device identifier, where the shared device identifier is shared by multiple receiver devices. The device may generate the link using information associated with the message. The device may provide the link to the receiver device after generating the link. The device may receive a request, from a requesting device, to access the message, the request including a device identifier associated with the requesting device. The device may selectively permit or prevent access to the message, by the requesting device, based on the receiver device identifier and the device identifier associated with the requesting device.
Abstract:
A device may receive an indication to generate a link associated with accessing a message. The message may be intended for a shared device identifier of a receiver device identified by a receiver device identifier, where the shared device identifier is shared by multiple receiver devices. The device may store information associating the message with the receiver device identifier. The device may generate the link using information associated with the message. The device may provide the link to the receiver device after generating the link. The device may receive a request, from a requesting device, to access the message, the request including a device identifier associated with the requesting device. The device may selectively permit or prevent access to the message, by the requesting device, based on the stored information and the device identifier associated with the requesting device.
Abstract:
A device may receive information associated with a user request to access a service using a first device. The information may include a user credential. The device may identify a second device associated with the user credential. The device may provide a notification, associated with the user request to access the service, to the second device, and may receive a response from the second device. The response may indicate to permit access to the service. The device may provide an instruction to permit the first device to access the service. The device may provide information that identifies services for which access has been permitted for the user credential. The device may receive an indication to prevent further access, for the user credential, to at least one service. The device may provide an instruction to prevent further access to the at least one service for the user credential.
Abstract:
A device can establish an identity for an individual by communicating with a first set of devices. The first set of devices can include a user device, a first server device associated with a certificate authority, or a second server device associated with an identity provider. The device can authenticate the identity of the individual by communicating with a second set of devices. The second set of devices can include the user device, or a third server device associated with a first service provider. The device can authorize the identity of the individual to be used by one or more service providers by communicating with a third set of devices. The third set of devices can include the user device, the third server device, or a fourth server device associated with a second service provider.
Abstract:
A device may receive network traffic information, associated with multiple transactions, that indicates, for each transaction of the multiple transactions, a credential and a source device identifier associated with the transaction. The device may determine, based on the network traffic information, a quantity of times that a common credential was used in two transactions occurring at different times and originating from different source devices. The device may provide information that identifies the quantity of times and the different source devices. The device may determine whether to block network traffic associated with a source device, of the different source devices, based on the quantity of times and/or user input received based on providing the information that identifies the quantity of times and the different source devices. The device may selectively provide an instruction to block the network traffic associated with the source device based on this determination.
Abstract:
An approach for simulating a telephony system to enable the evaluation of rules employed by the system for routing inbound calls to representatives is described. A simulation manager receives call production data, representative production data, or a combination thereof as generated by a telephony system during a production run for directing one or more inbound calls to one or more representatives. The simulation manager also generates an expected call handling response of the telephony system during a subsequent production run due to (a) one or more subsequent inbound calls, (b) a change associated with the one or more representatives, (c) a change associated with the call handling rules, or (d) a combination thereof based on execution of a simulation of the execution of the telephony system.
Abstract:
An approach is provided for enabling a subscriber to establish rules for controlling user interaction with a resource based on the activity of the user. A reactive control platform monitors a current activity of a user of a device, one or more services, or a combination thereof associated with a subscriber during access by the user to a network of a subscriber. The status of the user is determined based on the monitoring, profile information associated with the user, or a combination thereof. A request for input from the subscriber for specifying one or more rules to be enforced for affecting a use of the device, the one or more services, the network of the subscriber, or a combination thereof by the user is then generated based on the determination.