Abstract: When a user is attempting to access a server application, a challenge is received, in a browser, for a one or more login credentials to access a server application (e.g., a web page). For example, a user is requested to provide a user name and password to login to the server application. In response to the user providing the credentials via the browser, the login credentials are sent. If the credentials are validated, an access token is received by the browser from the server application. In response to receiving the access token for the server application, the browser sends the access token and an address for the server application, via a local loopback address, to a local application. This allows the local application to send local information, such as local files, to the server application using the token.

Abstract: Mechanisms are provided herein which accommodate the handling of multiple service errors on a service exception handling display. In particular, when a single and/or multiple service errors are present, a user interface of the communication device can provide a dynamic exceptions view for simple management and control of the one or more service errors received. The service errors can be resolved independently and a manner most productive with a user while improving user experience.

Abstract: To provide better administrative access control for allowing access to network applications, an authorization framework is extended by dynamically adding administrative access control to the authorization framework. For example, the authorization framework can be extended by adding a plug-in to the authorization framework. The authorization framework manages the access control by generating tokens. For example, a token may be a digital certificate. The tokens define what access control an application, such as a client application has when accessing the network application. The tokens are based on the dynamically added administrative access control. When a request for a token is securely received, the authorization framework generates a token that identifies if the application (e.g., the client application) is allowed or not allowed to access the network application. The token is then used by the application to access the network application.

Abstract: An indication of a change in a right to use a service or feature is received. For example, this can be based on an administrator granting access to a previously installed service or feature. In response, a notification is sent to a user of the change of the right to use the service or feature. The notification requests the user to provide a credential to approve the change of the right to use the service or feature. For example, a link may be provided in an email or text message that the user can click on to provide a password/user name. The credential is received and verified. In response to validating the credential, access is allowed according to the change of the right to use the service or feature. The user then has access to the service/feature without the administrator having to know the user's credential.

Abstract: When a user is attempting to access a server application, a challenge is received, in a browser, for a one or more login credentials to access a server application (e.g., a web page). For example, a user is requested to provide a user name and password to login to the server application. In response to the user providing the credentials via the browser, the login credentials are sent. If the credentials are validated, an access token is received by the browser from the server application. In response to receiving the access token for the server application, the browser sends the access token and an address for the server application, via a local loopback address, to a local application. This allows the local application to send local information, such as local files, to the server application using the token.

Abstract: An indication of a change in a right to use a service or feature is received. For example, this can be based on an administrator granting access to a previously installed service or feature. In response, a notification is sent to a user of the change of the right to use the service or feature. The notification requests the user to provide a credential to approve the change of the right to use the service or feature. For example, a link may be provided in an email or text message that the user can click on to provide a password/user name. The credential is received and verified. In response to validating the credential, access is allowed according to the change of the right to use the service or feature. The user then has access to the service/feature without the administrator having to know the user's credential.

Abstract: Telephonic and other endpoints often make presence information of other users available on the endpoint. Systems whereby every user sends a notification to every other user quickly becomes resource intensive. Providing presence information only to users subscribed to the presence of other users helps; but, maintaining such subscriptions is often overlooked. Providing automatic subscriptions based upon a triggering event allows presence information to be provided to associated users. The presence information may be time limited to allow for an appropriate amount of presence information to be provided for a duration most likely determined to be relevant. Upon expiration of the subscription, the utilized resources are released without requiring any human intervention.

Abstract: Mechanisms are provided herein which accommodate the handling of multiple service errors on a service exception handling display. In particular, when a single and/or multiple service errors are present, a user interface of the communication device can provide a dynamic exceptions view for simple management and control of the one or more service errors received. The service errors can be resolved independently and a manner most productive with a user while improving user experience.

Abstract: To provide better administrative access control for allowing access to network applications, an authorization framework is extended by dynamically adding administrative access control to the authorization framework. For example, the authorization framework can be extended by adding a plug-in to the authorization framework. The authorization framework manages the access control by generating tokens. For example, a token may be a digital certificate. The tokens define what access control an application, such as a client application has when accessing the network application. The tokens are based on the dynamically added administrative access control. When a request for a token is securely received, the authorization framework generates a token that identifies if the application (e.g., the client application) is allowed or not allowed to access the network application. The token is then used by the application to access the network application.