Usage tracking for software as a service (saas) applications

A method for tracking SaaS usage, the method comprising:

• providing a server that hosts a SaaS usage proxy;
• generating, by the SaaS usage proxy, a client that a user is able to access, wherein the user is an employee of an enterprise;
• receiving, by the SaaS usage proxy, known login credentials from the client that are input by the user;
• validating, by the SaaS usage proxy, the known login credentials;
• responsive to successfully validating the known login credentials, presenting, by the SaaS usage proxy, one or more SaaS applications available through the SaaS usage proxy to the user;
• generating, by the SaaS usage proxy, encrypted login credentials for a SaaS application selected by the user,
• wherein the encrypted login credentials are for one of a plurality of accounts for the SaaS application associated with the enterprise;
• supplying, by the SaaS usage proxy, the encrypted login credentials to a mapping table, which causes the encrypted login credentials to be matched to the known login credentials belonging to the user;
• providing the user access to the SaaS application and allowing the user to initiate the SaaS application through the SaaS usage proxy;
• inputting, by the SaaS usage proxy upon the SaaS application being initiated, the encrypted login credentials on behalf of the user,
• wherein inputting the encrypted login credentials logs the user into the SaaS application and grants the user access to the SaaS application, and
• wherein the encrypted login credentials remain unknown to the user;
• and
• monitoring, by the SaaS usage proxy, usage of the SaaS application by the user.

An authentication system comprising:

• a communication module communicatively coupled to a client that is presented on a network-accessible device and a SaaS application that is hosted by a server;
• an enterprise authentication module configured to validate a first set of credentials received from the client,
• wherein entry of the first set of credentials enables a user to view one or more SaaS applications available through a SaaS usage proxy, and
• wherein the first set of credentials is valid for an established enterprise-wide authentication system;
• and
• the SaaS usage proxy configured to:
• provide the client to the user;
• generate a second set of credentials for the SaaS application, wherein the second set of credentials are for one of a plurality of accounts for the SaaS application that are accessible to the user;
• encrypt the second set of credentials such that the second set of credentials remains unknown to the user;
• associate the second set of credentials with the first set of credentials;
• store the first set of credentials and the second set of credentials in a mapping table;
• allow the user to initiate the SaaS application using the client;
• log into the SaaS application by entering the second set of credentials on behalf of the user when the user elects to initiate the SaaS application;
• and
• track usage of the SaaS application by the user.