Managing the display of hidden proprietary software code to authorized licensed users
A method and system for allowing an independent software vendor (ISV) access to proprietary software code for software of an organization has been developed. An ISV generates a login request that masquerades as a user of the software. A license management system that controls access to the software, is accessed and determines if two session IDs are present. The presence of two separate session IDs identifies the ISV and if detected, the ISV is allowed access to the proprietary software code. Finally, the organization is notified about the ISV's access to the proprietary software code.
1. A method for regulating access by an independent software vendor (ISV) to proprietary source code for software of an organization, comprising:
receiving a login request from the ISV, where the login request masquerades as a user of the software;
accessing a license management system in response to the login request, where the license management system is capable of controlling access to the software;
determining the presence of two session identifiers (IDs) for the login request comprising a user session ID and a masquerade session ID, where the presence of two separate session IDs identifies the ISV;
accessing to the proprietary source code by the ISV with permission from the license management system, where the license management system limits access by the ISV to only the proprietary source code that was developed by the ISV; and
notifying the organization of access by the ISV to the proprietary source code.
2. The method of claim 1 , where the proprietary source code is written in an object oriented programming (OOP) language.
3. The method of claim 2 , where the proprietary source code comprises managed object classes.
4. The method of claim 1 , further comprising authorizing the ISV to troubleshoot the proprietary source code with permission from the license management system.
5. The method of claim 4 , wherein troubleshooting the proprietary source code comprises utilizing debugging tools by the ISV.
6. The method of claim 1 , further comprising authorizing the ISV to upgrade the proprietary source code with permission from the license management system.
7. A database system comprising a processor in communication with a memory element that has computer-executable instructions stored thereon and configurable to be executed by the processor to cause the database system to:
receive a login request from an independent software vendor (ISV), where the login request masquerades as a user of an organization's software;
access a license management system in response to the login request, where the license management system is capable of controlling access to proprietary software source code;
determine the presence of two session IDs for the login request comprising a user session ID and a masquerade session ID, where the presence of two separate session IDs identifies the ISV;
access to the proprietary source code by the ISV with permission from the license management system, where the license management system limits access by the ISV to only the proprietary source code that was developed by the ISV; and
notify the organization of access by the ISV to the proprietary software source code.
8. The database system of claim 7 , where the login request is received through an application program interface (API).
9. The database system of claim 7 , where the accessed proprietary software comprises a managed package.
10. The database system of claim 9 , where the proprietary source code is written in an object oriented programming (OOP) language.
11. The database system of claim 9 , where managed package comprises managed object classes.