REGISTERING A MOBILE APPLICATION WITH A SERVER

• US 20150040201A1
• Filed: 10/30/2013
• Published: 02/05/2015
• Est. Priority Date: 07/31/2013
• Status: Active Grant

• Current Assignee: SAP SE
• Original Assignee: SAP AG (SAP SE)
• Inventors: Nyisztor, Karoly, Kedefors, Hans, Hinrichs, Karsten, Hereb, Csaba, Palfi, Andras, Jozsa, Tamas
• Granted Patent: US 9,258,669 B2
• Time in Patent Office: Days
• US Class Current: 726/7
• CPC Class Codes: G06F 8/36 Software reuse
• CPC Class Codes: G06F 8/60 Software deployment
• CPC Class Codes: G06F 8/65 Updates security arrangements therefor G06F21/57
• CPC Class Codes: G06F 8/71 Version control security arrangements therefor G06F21/57; Configuration management
• CPC Class Codes: G06F 9/44505 Configuring for program initiating, e.g. using registry, configuration files
• CPC Class Codes: H04L 41/082 the condition being updates or upgrades of network functionality
• CPC Class Codes: H04L 63/08 for authentication of entities cryptographic mechanisms or cryptographic arrangements for entity authentication H04L9/32
• CPC Class Codes: H04L 67/34 involving the movement of software or configuration parameters network booting or remote initial program loading [RIPL] G06F9/4416
• CPC Class Codes: H04W 4/60 Subscription-based services using application servers or record carriers, e.g. SIM application toolkits

Abstract

In an example embodiment, a test request is sent to a server configured to provide data to the mobile device application. Then a response to the test request is received from the server. The response is analyzed to identify a pattern in the response indicative of a communication sent via a particular communication path. An available communication path between the mobile device application and the server corresponding to the pattern is identified. Then, a mobile device application is registered with the server via the identified communication path.

Claims

1. A method performed by a mobile device application, comprising:

sending a test request to a server configured to provide data to the mobile device application;

receiving a response to the test request from the server;

analyzing the response to the test request to identify a pattern in the response indicative of a communication sent via a particular communication path;

identifying an available communication path between the mobile device application and the server corresponding to the pattern; and

registering the mobile device application with the server via the identified communication path.

2. The method of claim 1, wherein registering the mobile device application with the server via the identified communication path includes:

registering the mobile device application using authorization credentials provided by a user, the authorization credentials used to register the user with a service provided by the server via the mobile device application;

accessing the authorization credentials for the user of the mobile device application; and

storing the mobile device application and the authorization credentials in a password-protected location of a mobile device that provides the mobile device application.

3. The method of claim 2, wherein storing the mobile device application and the authorization credentials in a password-protected location supported by the mobile device includes assigning a passcode to the mobile device application having a syntax that follows password policy rules applied to the mobile device application.

4. The method of claim 2, wherein the password-protected location only contains contents of the mobile device application and the authorization credentials.

5. The method of claim 2, wherein the authorization credentials include a username and password provided by the user that are used by the mobile device application to register the user with the service provided by the server via the mobile application.

6. The method of claim 1, wherein the pattern includes header information, code, or cookie information within the response to the test request that is indicative of a gateway communication path.

7. The method of claim 1, wherein the pattern includes header information, code, or cookie information within the response to the test request that is indicative of a mobile platform communication path.

8. The method of claim 1, wherein the pattern includes header information, code, or cookie information within the response to the test request that is indicative of a gateway communication path and an Internet Information Services (IIS) server type.

9. The method of claim 1, wherein the pattern includes header information, code, or cookie information within the response to the test request that is indicative of a gateway communication path and an Apache server type.

10. The method of claim 1, wherein sending the test request to the server configured to provide data to the mobile device application includes sending a request that includes plist information provided by a user associated with the mobile device application;

and wherein receiving the response to the test request from the server includes receiving a response from the server that includes the pattern.

11. A logon manager comprising:

a test request module executable by a processor and configured to send a test request to a server configured to provide data to a mobile device application;

a server response module configured to receive a response to the test request from the server;

a path identification module configured to analyze the response to the test request to identify a pattern in the response indicative of a communication sent via a particular communication path, and identify an available communication path between the mobile device application and the server corresponding to the pattern; and

a registration module configured to register the mobile device application with the server via the identified communication path.

12. The logon manager of claim 11, wherein the logon manager is located within a deployable unit containing custom code and a mobile application framework.

13. The logon manager of claim 11, wherein the registration module is further configured to:

register the mobile device application using authorization credentials provided by a user, the authorization credentials used to register the user with a service provided by the server via the mobile device application;

access the authorization credentials for the user of the mobile device application; and

store the mobile device application and the authorization credentials in a password-protected location of a mobile device that provides the mobile device application.

14. The logon manager of claim 13, wherein storing the mobile device application and the authorization credentials in a password-protected location supported by the mobile device includes assigning a passcode to the mobile device application having a syntax that follows password policy rules applied to the mobile device application.

15. The logon manager of claim 13, wherein the password-protected location only contains contents of the mobile device application and the authorization credentials.

16. A non-transitory machine-readable storage medium comprising instructions, which when implemented by one or more machines, cause the one or more machines to perform operations comprising:

sending a test request to a server configured to provide data to a mobile device application;

receiving a response to the test request from the server;

analyzing the response to the test request to identify a pattern in the response indicative of a communication sent via a particular communication path;

identifying an available communication path between the mobile device application and the server corresponding to the pattern; and

registering the mobile device application with the server via the identified communication path.

17. The non-transitory machine-readable storage medium of claim 16, wherein registering the mobile device application with the server via the identified communication path includes:

registering the mobile device application using authorization credentials provided by a user, the authorization credentials used to register the user with a service provided by the server via the mobile device application;

accessing the authorization credentials for the user of the mobile device application; and

storing the mobile device application and the authorization credentials in a password-protected location of a mobile device that provides the mobile device application.

18. The non-transitory machine-readable storage medium of claim 17, wherein storing the mobile device application and the authorization credentials in a password-protected location supported by the mobile device includes assigning a passcode to the mobile device application having a syntax that follows password policy rules applied to the mobile device application.

19. The non-transitory machine-readable storage medium of claim 18, wherein the password-protected location only contains contents of the mobile device application and the authorization credentials.

20. The non-transitory machine-readable storage medium of claim 17, wherein the authorization credentials include a username and password provided by the user that are used by the mobile device application to register the user with the service provided by the server via the mobile device application.