System and method to allow third-party developer to debug code in customer environment

Patent metadata

Field	Value
Publication number	US-10547601-B2
Application number	US-201615394307-A
Country	US
Kind code	B2
Filing date	Dec 29, 2016
Priority date	Jun 6, 2016
Publication date	Jan 28, 2020
Grant date	Jan 28, 2020

Abstract

A platform is provided to allow the developer to log into a subscriber's computer system by using the credential of the developer or the subscriber to view and to debug at least a portion of executable code that is used by the subscriber. The executable code used by the subscriber may be part of managed package code, at least portions of which are customized for various subscribers. Cooperative debugging may be provided between developer and subscriber with lifting of code encapsulation for the developer in the subscriber implementation. The developer and the subscriber may be granted debugging licenses each authorizing a limited number of debugging sessions, and each debugging session run by the developer may be counted against the debugging license of either the developer or the subscriber. Debugging licenses may be transferred between the developer and the subscriber.

First claim

The invention claimed is:

1. A method for a developer to debug code in a data processing system of a subscriber, the method comprising:
receiving, at the data processing system, a request from the subscriber to debug a set of code used by the subscriber;
receiving, at the data processing system, an indication of authentication of the developer to access the set of code based on a subscriber permission setting;
providing, by the data processing system, the developer with a permission to run a debugging tool on the set of code used by the subscriber upon receiving the indication of authentication;
providing, by the data processing system, access by the developer to view the set of code that is hosted by the data processing system and used by the subscriber; and
creating, by the data processing system, a debugging session to permit the developer to run the debugging tool on the set of code,
wherein the subscriber accesses the data processing system using a credential assigned to the subscriber, and
the subscriber is separate from the developer.

2. The method of claim 1 , further comprising receiving, at the data processing system, a request from the developer to select the subscriber from a plurality of subscribers.

3. The method of claim 1 , wherein providing, by the data processing system, access to the developer to view the set of code that is hosted by the data processing system and used by the subscriber comprises permitting the developer to log in to the debugger session using a credential of the developer.

4. The method of claim 1 , wherein providing, by the data processing system, access to the developer to view the set of code that is hosted by the data processing system and used by the subscriber comprises permitting the developer to log in to the debugger session using the credential of the subscriber.

5. The method of claim 1 , wherein the developer is permitted to run an authorized number of debugging sessions, further comprising decreasing the authorized number of debugging sessions by one upon creating, by the data processing system, the debugging session to permit the developer to run the debugging tool on the set of code.

6. The method of claim 1 , wherein the subscriber is permitted to run an authorized number of debugging sessions, further comprising decreasing the authorized number of debugging sessions by one upon creating, by the data processing system, the debugging session to permit the developer to run the debugging tool on the set of code.

7. The method of claim 1 , wherein the developer is permitted to run a first authorized number of debugging sessions and the subscriber is permitted to run a second authorized number of debugging sessions, further comprising transferring at least one authorized debugging session between the developer and the subscriber.

8. The method of claim 1 , further comprising preventing, by the data processing system, the developer from running more than one debugging session at a time.

9. The method of claim 1 , further comprising terminating, by the data processing system, the debugging session upon expiration of a limited time.

10. The method of claim 1 , further comprising terminating, by the data processing system, the debugging session upon occurrence of an execution error.

11. The method of claim 1 , wherein the set of code comprises a portion of managed package code customized for the subscriber.

12. The method of claim 11 , wherein the developer is prevented from viewing another portion of the managed package code other than the set of code customized for the subscriber.

13. The method of claim 11 , wherein the developer is prevented from debugging another portion of the managed package code other than the set of code customized for the subscriber.

14. The method of claim 1 , wherein the set of code comprises a portion of managed package code, and wherein another portion of the managed package code is not authorized for access by the developer, further comprising redacting the other portion of the managed package code that is not authorized for access by the developer.

15. The method of claim 1 , wherein the developer is permitted to run an authorized debugging session across a plurality of computers or servers of the subscriber with a session identification.

16. The method of claim 1 , further comprising transferring, by the data processing system, a namespace between the developer and the subscriber.

17. The method of claim 1 , further comprising transferring, by the data processing system, a uniform resource locator (URL) for the debugging session to an integrated development environment (IDE) to create the debugging session.

18. An apparatus for a developer to debug code in a data processing system of a subscriber, the system comprising:
a processor; and
a memory communicably coupled to the processor, the memory including computer instructions configured to cause the processor to:
receive a request from the subscriber to debug a set of code used by the subscriber;
receive an indication of authentication of the developer to access the set of code based on a subscriber permission setting;
provide the developer with a permission to run a debugging tool on the set of code used by the subscriber upon receiving the indication of authentication;
provide access by the developer to view the set of code that is hosted by the data processing system and used by the subscriber; and
create a debugging session to permit the developer to run the debugging tool on the set of code,

wherein the subscriber accesses the data processing system using a credential assigned to the subscriber, and
the subscriber is separate from the developer.

19. The apparatus of claim 18 , wherein the computer instructions to provide access to the developer to view the set of code that is hosted by the data processing system and used by the subscriber comprise computer instructions to permit the developer to log in to the debugger session using a credential of the developer.

20. The apparatus of claim 18 , wherein the computer instructions to provide access to the developer to view the set of code that is hosted by the data processing system and used by the subscriber comprise computer instructions to permit the developer to log in to the debugger session using the credential of the subscriber.

21. The apparatus of claim 18 , wherein the developer is permitted to run an authorized number of debugging sessions, and wherein the computer instructions further comprise computer instructions to decrease the authorized number of debugging sessions by one upon creating the debugging session to permit the developer to run the debugging tool on the set of code.

22. The apparatus of claim 18 , wherein the subscriber is permitted to run an authorized number of debugging sessions, and wherein the computer instructions further comprise computer instructions to decrease the authorized number of debugging sessions by one upon creating the debugging session to permit the developer to run the debugging tool on the set of code.

23. The apparatus of claim 18 , wherein the developer is permitted to run a first authorized number of debugging sessions and the subscriber is permitted to run a second authorized number of debugging sessions, and wherein the computer instructions further comprise computer instructions to transfer at least one authorized debugging session between the developer and the subscriber.

24. The apparatus of c

Assignees

• Salesforce Com Inc

Inventors

• Lipke Nathan Edward
• Baker David Ross
• Chen Nicholas Chun Yuan
• Widjaja Jonathan
• Chow Winston
• Kaplan Josh
• Wester Gregory

Classifications

• H04L63/08 Primary

  for authentication of entities (cryptographic mechanisms or cryptographic arrangements for entity authentication H04L9/32) · CPC title

• G06F21/10

  Protecting distributed programs or content, e.g. vending or licensing of copyrighted material (protection in video systems or pay television H04N7/16) {; Digital rights management [DRM]} · CPC title

• G06F21/629

  to features or functions of an application · CPC title

• G06F11/362

  Debugging of software · CPC title

• H04L2463/103

  applying security measure for protecting copyright · CPC title