An email-based automated recovery action may provide a mechanism for authorizing operations in a hosted environment. In conventional systems, engineers and operators are typically allowed to perform only certain read-only operations in the hosted environment in order to minimize service disruptions. When a service incident occurs, however, engineers are not allowed to perform certain automated recovery actions in the environment by an automation framework. Thus, in some situations, the limits enforced by the automation framework may result in greater service disruption due to an engineer's or operator's inability to repair an active problem.
This Summary is provided to introduce a selection of concepts in a simplified form that are further described below in the Detailed Description. This Summary is not intended to identify key features or essential features of the claimed subject matter. Nor is this Summary intended to be used to limit the claimed subject matter's scope.
Email-based recovery actions may be provided. A request from a user to perform an action may be received. If the user is determined not to have permission to perform the action, a message may be sent to a second user to approve the requested action. If the second user approves the requested action, the requested action may be performed.
Both the foregoing general description and the following detailed description provide examples and are explanatory only. Accordingly, the foregoing general description and the following detailed description should not be considered to be restrictive. Further, features or variations may be provided in addition to those set forth herein. For example, embodiments may be directed to various feature combinations and sub-combinations described in the detailed description.
The accompanying drawings, which are incorporated in and constitute a part of this disclosure, illustrate various embodiments of the present invention. In the drawings:
The following detailed description refers to the accompanying drawings. Wherever possible, the same reference numbers are used in the drawings and the following description to refer to the same or similar elements. While embodiments of the invention may be described, modifications, adaptations, and other implementations are possible. For example, substitutions, additions, or modifications may be made to the elements illustrated in the drawings, and the methods described herein may be modified by substituting, reordering, or adding stages to the disclosed methods. Accordingly, the following detailed description does not limit the invention. Instead, the proper scope of the invention is defined by the appended claims.
Email-based recovery actions may allow engineers (e.g., product developers) and operators (e.g., support personnel, IT, and/or technicians) to perform normally prohibited disruptive actions on application servers, such as e-mail and/or web servers. For example, an engineer may need to restart an e-mail processing service to apply a critical update, but may normally not have permission to take such a production service offline. Upon receiving the engineer's request, an automation framework may recognize that the engineer does not have the required permission. Instead of denying the request, the automation framework may forward the request to an approval manager. For example, an e-mail, instant message, text message, and/or web alert may be sent and/or displayed to the approval manager. The approval manager may evaluate the request and then approve or deny the engineer's ability to perform the disruptive action. Such an approval may comprise a one-time approval, the engineer may be approved to perform the same action for a limited time window, and/or the engineer may be granted permanent permissions to perform such actions in the future.
From stage 210, method 200 may advance to stage 215 where computing device 300 may determine whether the first user has permission to perform the action. For example, automation framework 110 may determine whether operator 125 belongs to an administrative user group. Each user group may comprise a set of permissions recorded in permissions database 114 that may control what actions the users associated with that group may perform. For example, users belonging to an operator user group may be allowed to read log entries associated with application servers 140(A)-(C) but may not be allowed to start or stop those services. Consistent with embodiments of the invention, different users and/or groups may have different permissions for different application servers. Users belonging to an administrative user group may have elevated permissions, including the ability to perform actions that may result in service disruptions.
If, at stage 215, computing device 300 determines that the user does not have permission to perform the action, method 200 may advance to stage 220 were computing device 300 may send an approval request to at least one second user. For example, the approval request may comprise a problem summary received from the first user and a command text associated with the requested action. Automation framework 110 may send the approval request via email over network 130 to approval manager 135.
Method 200 may then advance to stage 225 where computing device 300 may receive a response to the approval request from the at least one second user. For example, approval manager 135 may reply to the email approving or denying the request. For another example, approval manager 135 may simply select a user interface control associated with the email message indicating whether they approve or deny the request, much as a meeting request may be accepted or rejected.
Method 200 may then advance to stage 230 where computing device 300 may determine whether the at least one second user has approved the requested action. For example, approval manager 135 may review the details of the requested action and approve the performance of the requested action.
In response to determining that the at least one second user has approved the requested action, or after determining that the user has sufficient permissions to perform the requested action, method 200 may advance to stage 235 where computing device 300 may perform the requested action. For example, automation framework 110 may execute the requested restart action on application server 140(A).
After performing the action at stage 235, or if the request was denied at stage 230, method 200 may advance to stage 240 where computing device 300 may create a log entry associated with the requested action. For example, the log entry may comprise a name of the first user, a name of the second user, the problem summary received from the first user, the command text associated with the requested action, and/or a result associated with performing the requested action.
An embodiment consistent with the invention may comprise a system for providing email-based recovery actions. The system may comprise a memory storage and a processing unit coupled to the memory storage. The processing unit may be operative to receive a request from a user to perform an action, determine whether the user has permission to perform the action, and in response to determining that the user does not have permission to perform the action, send a message to a second user to approve the requested action. The processing unit may be further operative to determine whether the second user has approved the requested action, and, in response to determining that the second user has approved the requested action, perform the requested action. The approval message may be sent, for example, as an e-mail message, an instant message, a web page notification, and/or a text message. The approval or denial of the request may be received by the same and/or a different channel than the request was originally sent. Being operative to determine whether the user has permission to perform the action may comprises being operative to determine whether the user is associated with an administrative user group. The approval and/or denial of the request may be logged along with the user who requested the action, the user who approved/denied the action, and/or a result of performing the action.
Another embodiment consistent with the invention may comprise a system for providing email-based recovery actions. The system may comprise a memory storage and a processing unit coupled to the memory storage. The processing unit may be operative to receive an action request from a first user, determine whether the first user has permission to perform the action, and in response to determining that the user does not have permission to perform the action, send an approval request to at least one second user via email to approve the requested action, receive a response to the approval request from the at least one second user via email, and determine whether the at least one second user has approved the requested action. In response to determining that the at least one second user has approved the requested action, the processing unit may be operative to perform the requested action. The approval request may comprise an impact analysis associated with performing the action request, a problem summary associated with the action request received from the first user, and/or a command text associated with the requested action. For example, the approval request may comprise the exact wording of the command associated with performing the requested action. The action request may be associated with an application service, such as a web server and/or an e-mail server. The approval request may be sent to a plurality of users each of whom may be associated with an administrative user group.
Yet another embodiment consistent with the invention may comprise a system for providing email-based recovery actions. The system may comprise a memory storage and a processing unit coupled to the memory storage. The processing unit may be operative to receive an action request from a first user, determine whether the first user has permission to perform the action, and, in response to determining that the user does not have permission to perform the action, send an approval request to at least one second user to approve the requested action, receive a response to the approval request from the at least one second user, and determine whether the at least one second user has approved the requested action. In response to determining that the at least one second user has approved the requested action, the processing unit may be operative to perform the requested action and create a log entry associated with the requested action. The log entry may comprise a name of the first user, a name of the second user, the problem summary received from the first user, the command text associated with the requested action, and a result associated with performing the requested action. In response to determining that the user does have permission to perform the action, the processing unit may be operative to perform the action and log the performance of the action.
With reference to
Computing device 300 may have additional features or functionality. For example, computing device 300 may also include additional data storage devices (removable and/or non-removable) such as, for example, magnetic disks, optical disks, or tape. Such additional storage is illustrated in
The term computer readable media as used herein may include computer storage media. Computer storage media may include volatile and nonvolatile, removable and non-removable media implemented in any method or technology for storage of information, such as computer readable instructions, data structures, program modules, or other data. System memory 304, removable storage 309, and non-removable storage 310 are all computer storage media examples (i.e memory storage.) Computer storage media may include, but is not limited to, RAM, ROM, electrically erasable read-only memory (EEPROM), flash memory or other memory technology, CD-ROM, digital versatile disks (DVD) or other optical storage, magnetic cassettes, magnetic tape, magnetic disk storage or other magnetic storage devices, or any other medium which can be used to store information and which can be accessed by computing device 300. Any such computer storage media may be part of device 300. Computing device 300 may also have input device(s) 312 such as a keyboard, a mouse, a pen, a sound input device, a touch input device, etc. Output device(s) 314 such as a display, speakers, a printer, etc. may also be included. The aforementioned devices are examples and others may be used.
The term computer readable media as used herein may also include communication media. Communication media may be embodied by computer readable instructions, data structures, and/or program modules, and includes any information delivery media. By way of example, and not limitation, communication media may include wired media such as a wired network or direct-wired connection, and wireless media such as acoustic, radio frequency (RF), infrared, and other wireless media.
As stated above, a number of program modules and data files may be stored in system memory 304, including operating system 305. While executing on processing unit 302, programming modules 306 (e.g., automation framework 110) may perform processes including, for example, one or more of method 300's stages as described above. The aforementioned process is an example, and processing unit 302 may perform other processes. Other programming modules that may be used in accordance with embodiments of the present invention may include electronic mail and contacts applications, word processing applications, spreadsheet applications, database applications, slide presentation applications, drawing or computer-aided application programs, etc.
Generally, consistent with embodiments of the invention, program modules may include routines, programs, components, data structures, and other types of structures that may perform particular tasks or that may implement particular abstract data types. Moreover, embodiments of the invention may be practiced with other computer system configurations, including hand-held devices, multiprocessor systems, microprocessor-based or programmable consumer electronics, minicomputers, mainframe computers, and the like. Embodiments of the invention may also be practiced in distributed computing environments where tasks are performed by remote processing devices that are linked through a communications network. In a distributed computing environment, program modules may be located in both local and remote memory storage devices.
Furthermore, embodiments of the invention may be practiced in an electrical circuit comprising discrete electronic elements, packaged or integrated electronic chips containing logic gates, a circuit utilizing a microprocessor, or on a single chip containing electronic elements or microprocessors. Embodiments of the invention may also be practiced using other technologies capable of performing logical operations such as, for example, AND, OR, and NOT, including but not limited to mechanical, optical, fluidic, and quantum technologies. In addition, embodiments of the invention may be practiced within a general purpose computer or in any other circuits or systems.
Embodiments of the invention, for example, may be implemented as a computer process (method), a computing system, or as an article of manufacture, such as a computer program product or computer readable media. The computer program product may be a computer storage media readable by a computer system and encoding a computer program of instructions for executing a computer process. The computer program product may also be a propagated signal on a carrier readable by a computing system and encoding a computer program of instructions for executing a computer process. Accordingly, the present invention may be embodied in hardware and/or in software (including firmware, resident software, micro-code, etc.). In other words, embodiments of the present invention may take the form of a computer program product on a computer-usable or computer-readable storage medium having computer-usable or computer-readable program code embodied in the medium for use by or in connection with an instruction execution system. A computer-usable or computer-readable medium may be any medium that can contain, store, communicate, propagate, or transport the program for use by or in connection with the instruction execution system, apparatus, or device.
The computer-usable or computer-readable medium may be, for example but not limited to, an electronic, magnetic, optical, electromagnetic, infrared, or semiconductor system, apparatus, device, or propagation medium. More specific computer-readable medium examples (a non-exhaustive list), the computer-readable medium may include the following: an electrical connection having one or more wires, a portable computer diskette, a random access memory (RAM), a read-only memory (ROM), an erasable programmable read-only memory (EPROM or Flash memory), an optical fiber, and a portable compact disc read-only memory (CD-ROM). Note that the computer-usable or computer-readable medium could even be paper or another suitable medium upon which the program is printed, as the program can be electronically captured, via, for instance, optical scanning of the paper or other medium, then compiled, interpreted, or otherwise processed in a suitable manner, if necessary, and then stored in a computer memory.
Embodiments of the present invention, for example, are described above with reference to block diagrams and/or operational illustrations of methods, systems, and computer program products according to embodiments of the invention. The functions/acts noted in the blocks may occur out of the order as shown in any flowchart. For example, two blocks shown in succession may in fact be executed substantially concurrently or the blocks may sometimes be executed in the reverse order, depending upon the functionality/acts involved.
While certain embodiments of the invention have been described, other embodiments may exist. Furthermore, although embodiments of the present invention have been described as being associated with data stored in memory and other storage mediums, data can also be stored on or read from other types of computer-readable media, such as secondary storage devices, like hard disks, floppy disks, or a CD-ROM, a carrier wave from the Internet, or other forms of RAM or ROM. Further, the disclosed methods' stages may be modified in any manner, including by reordering stages and/or inserting or deleting stages, without departing from the invention.
All rights including copyrights in the code included herein are vested in and the property of the Applicants. The Applicants retain and reserve all rights in the code included herein, and grants permission to reproduce the material only in connection with reproduction of the granted patent and for no other purpose.
While the specification includes examples, the invention's scope is indicated by the following claims. Furthermore, while the specification has been described in language specific to structural features and/or methodological acts, the claims are not limited to the features or acts described above. Rather, the specific features and acts described above are disclosed as example for embodiments of the invention.
Number | Name | Date | Kind |
---|---|---|---|
5423044 | Sutton et al. | Jun 1995 | A |
5564016 | Korenshtein | Oct 1996 | A |
5911143 | Deinhart et al. | Jun 1999 | A |
6151643 | Cheng et al. | Nov 2000 | A |
6335972 | Chandersekaran et al. | Jan 2002 | B1 |
6678826 | Kelly et al. | Jan 2004 | B1 |
6694437 | Pao et al. | Feb 2004 | B1 |
6804773 | Grigsby et al. | Oct 2004 | B1 |
6978367 | Hind et al. | Dec 2005 | B1 |
7205883 | Bailey | Apr 2007 | B2 |
7257713 | Colvig et al. | Aug 2007 | B2 |
7426654 | Adams, Jr. et al. | Sep 2008 | B2 |
7526685 | Noy et al. | Apr 2009 | B2 |
7630480 | Fleck et al. | Dec 2009 | B2 |
7680822 | Vyas et al. | Mar 2010 | B1 |
7698430 | Jackson | Apr 2010 | B2 |
7702736 | Ouchi | Apr 2010 | B2 |
7734670 | Poozhiyil et al. | Jun 2010 | B2 |
7815106 | McConnell | Oct 2010 | B1 |
7831833 | Gaylor | Nov 2010 | B2 |
7950051 | Spitz et al. | May 2011 | B1 |
7992008 | Ashok et al. | Aug 2011 | B2 |
8046558 | Ghose | Oct 2011 | B2 |
8195488 | Taix et al. | Jun 2012 | B1 |
8201224 | Spertus | Jun 2012 | B1 |
8296827 | Paganetti et al. | Oct 2012 | B2 |
8310923 | Nordstrom et al. | Nov 2012 | B1 |
8438647 | Jevans | May 2013 | B2 |
8458455 | Anderson et al. | Jun 2013 | B2 |
8458779 | Valentine et al. | Jun 2013 | B2 |
8793790 | Khurana et al. | Jul 2014 | B2 |
8839257 | Lukyanov et al. | Sep 2014 | B2 |
8881249 | Nunn et al. | Nov 2014 | B2 |
20010021926 | Schneck et al. | Sep 2001 | A1 |
20020026592 | Gavrila et al. | Feb 2002 | A1 |
20020035521 | Powers | Mar 2002 | A1 |
20020147801 | Gullotta et al. | Oct 2002 | A1 |
20030037251 | Frieder et al. | Feb 2003 | A1 |
20030115148 | Takhar | Jun 2003 | A1 |
20030139962 | Nobrega et al. | Jul 2003 | A1 |
20040230530 | Searl et al. | Nov 2004 | A1 |
20050050354 | Gociman | Mar 2005 | A1 |
20050154744 | Morinville | Jul 2005 | A1 |
20050193041 | Bourbonnais et al. | Sep 2005 | A1 |
20060005048 | Osaki et al. | Jan 2006 | A1 |
20060048224 | Duncan et al. | Mar 2006 | A1 |
20060075144 | Challener et al. | Apr 2006 | A1 |
20060137007 | Paatero et al. | Jun 2006 | A1 |
20060168079 | Shen et al. | Jul 2006 | A1 |
20060184675 | Salmre et al. | Aug 2006 | A1 |
20060242690 | Wolf et al. | Oct 2006 | A1 |
20060265599 | Kanai | Nov 2006 | A1 |
20070028293 | Boerries et al. | Feb 2007 | A1 |
20070083928 | Mattsson et al. | Apr 2007 | A1 |
20070094334 | Hoffman et al. | Apr 2007 | A1 |
20070101434 | Jevans | May 2007 | A1 |
20070124361 | Lowry et al. | May 2007 | A1 |
20070180100 | Biggs et al. | Aug 2007 | A1 |
20070185875 | Chang et al. | Aug 2007 | A1 |
20070192416 | Gupta | Aug 2007 | A1 |
20070250920 | Lindsay | Oct 2007 | A1 |
20070289019 | Lowrey | Dec 2007 | A1 |
20070294258 | Caldwell et al. | Dec 2007 | A1 |
20080098485 | Chiou | Apr 2008 | A1 |
20080103916 | Camarador et al. | May 2008 | A1 |
20080123854 | Peel et al. | May 2008 | A1 |
20080140778 | Banavar et al. | Jun 2008 | A1 |
20080154774 | Dennison et al. | Jun 2008 | A1 |
20080155685 | Beilinson et al. | Jun 2008 | A1 |
20080168532 | Carter et al. | Jul 2008 | A1 |
20080195936 | White et al. | Aug 2008 | A1 |
20080276098 | Florencio et al. | Nov 2008 | A1 |
20080287121 | Ebrom et al. | Nov 2008 | A1 |
20080320310 | Florencio et al. | Dec 2008 | A1 |
20090048881 | Keane et al. | Feb 2009 | A1 |
20090055822 | Tolman et al. | Feb 2009 | A1 |
20090094667 | Habeck et al. | Apr 2009 | A1 |
20090104888 | Cox | Apr 2009 | A1 |
20090119541 | Inoue et al. | May 2009 | A1 |
20090193407 | Lepeska | Jul 2009 | A1 |
20090210427 | Elder et al. | Aug 2009 | A1 |
20090249284 | Antosz et al. | Oct 2009 | A1 |
20090271451 | Young et al. | Oct 2009 | A1 |
20090319402 | Manista et al. | Dec 2009 | A1 |
20090320088 | Gill et al. | Dec 2009 | A1 |
20090320107 | Corella | Dec 2009 | A1 |
20090328023 | Bestland et al. | Dec 2009 | A1 |
20100005510 | Weber et al. | Jan 2010 | A1 |
20100011418 | Despain et al. | Jan 2010 | A1 |
20100017589 | Reed et al. | Jan 2010 | A1 |
20100023368 | Houba | Jan 2010 | A1 |
20100031058 | Kito et al. | Feb 2010 | A1 |
20100037056 | Follis et al. | Feb 2010 | A1 |
20100063950 | Joshi et al. | Mar 2010 | A1 |
20100064072 | Tang et al. | Mar 2010 | A1 |
20100087941 | Assaf et al. | Apr 2010 | A1 |
20100091318 | Ferlitsch | Apr 2010 | A1 |
20100169630 | Mirashrafi et al. | Jul 2010 | A1 |
20100185451 | Choi et al. | Jul 2010 | A1 |
20100188287 | Madsen et al. | Jul 2010 | A1 |
20100205421 | Campbell et al. | Aug 2010 | A1 |
20100212008 | Jaganathan et al. | Aug 2010 | A1 |
20100218012 | Joseph et al. | Aug 2010 | A1 |
20100242041 | Plondke et al. | Sep 2010 | A1 |
20100250939 | Adams et al. | Sep 2010 | A1 |
20100257346 | Sosnosky et al. | Oct 2010 | A1 |
20100257579 | Karjoth et al. | Oct 2010 | A1 |
20100257596 | Ngo et al. | Oct 2010 | A1 |
20100278078 | Proulx et al. | Nov 2010 | A1 |
20110023107 | Chen et al. | Jan 2011 | A1 |
20110061093 | Korkus et al. | Mar 2011 | A1 |
20110078497 | Lyne et al. | Mar 2011 | A1 |
20110099552 | Avni et al. | Apr 2011 | A1 |
20110099616 | Mazur et al. | Apr 2011 | A1 |
20110126111 | Gill et al. | May 2011 | A1 |
20110191254 | Womack | Aug 2011 | A1 |
20110246426 | Cho | Oct 2011 | A1 |
20110247066 | Lee | Oct 2011 | A1 |
20110252404 | Park et al. | Oct 2011 | A1 |
20110289588 | Sahai et al. | Nov 2011 | A1 |
20110302632 | Garrett et al. | Dec 2011 | A1 |
20120016621 | Tan et al. | Jan 2012 | A1 |
20120096306 | Akirav et al. | Apr 2012 | A1 |
20120144234 | Clark et al. | Jun 2012 | A1 |
20120185911 | Polite et al. | Jul 2012 | A1 |
20120185933 | Belk et al. | Jul 2012 | A1 |
20120209884 | Mattsson et al. | Aug 2012 | A1 |
20120239822 | Poulson et al. | Sep 2012 | A1 |
20120259720 | Nuzzi | Oct 2012 | A1 |
20120266246 | Amit et al. | Oct 2012 | A1 |
20120317132 | Brady et al. | Dec 2012 | A1 |
20130024918 | Cramer et al. | Jan 2013 | A1 |
20130024947 | Holland et al. | Jan 2013 | A1 |
20130031070 | Ducharme et al. | Jan 2013 | A1 |
20130111260 | Reddy et al. | May 2013 | A1 |
20130132963 | Lukyanov et al. | May 2013 | A1 |
20130133024 | MacLeod et al. | May 2013 | A1 |
20130239166 | MacLeod et al. | Sep 2013 | A1 |
20140165167 | Nunn et al. | Jun 2014 | A1 |
Entry |
---|
U.S. Application entitled “Instance-Based Command Execution, Approval, and Notification Framework,” having U.S. Appl. No. 13/154,660, filed Jun. 7, 2011. |
Huhns, M., et al.; “Service-Oriented Computing: Key Concepts and Principles”; IEEE Internet Computing Jan./Feb. 2005, IEEE Computer Society; 7 pgs. |
Wright, T.; “System Center Service Manager 2010 Release Candidate Released!!”; Microsoft Corporation; Mar. 3, 2010; 3 pgs. |
Kaufman, Charlie, et al.; “Windows Azure™ Security Overview”; Published Aug. 2010; 24 pgs. Obtained at: http://www.globalfoundationservices.com/security/documents/WindowsAzureSecurityOverview1—0Aug2010.pdf. |
Publication entitled; “PCI DSS Compliance in the UNIX/LINUX Datacenter Environment”; Published Aug. 2009 by BeyondTrust Corporation; 19 pgs. Obtained at: http://i.zdnet.com/whitepapers/BeyondTrust—PCIDSSComplianceintheUNIXLinuxDatacenterEnvironment.pdf. |
Wright, T.; “System Center Service Manager 2010 Release Candidate Released!! ”; Microsoft Corporation; Mar. 3, 2010; 3 pgs. |
U.S. Appl. No. 13/301,872, filed Nov. 22, 2011, entitled “Auto-Approval of Recovery Actions Based on an Extensible Set of Conditions and Policies”. |
U.S. Appl. No. 13/302,064, filed Nov. 22, 2011, entitled “Superseding of Recovery Actions Based on Aggregation of Requests for Automated Sequencing and Cancellation”. |
U.S. Appl. No. 13/413,078, filed Mar. 6, 2012, entitled “Operating Large Scale Systems and Cloud Service with Zero-Standing Elevated Permissions”. |
Stanger, Mark, article entitled “Change Management Workflow Approval Scripts in Service-now.com” Published on Oct. 20, 2010. Available at: http://www.servicenowguru.com/scripting/change-management-workflow-approval-scripts-servicenowcom/. |
“Change Management Process” Version 1.0—Published Date: May 1, 2006. Available at: http://its.uncg.edu/Service—Management/Change/ChangeManagementProcess.pdf. |
Kadar, et al, article entitled “Automatic Classification of Change Requests for Improved IT Service Quality”—Published Date: Mar. 29, 2011. In proceedings of Annual SRII Global Conference, Mar. 29, 2011, pp. 430-439. Available at: http://ieeexplore.ieee.org/stamp/stamp.jsp?tp=&arnumber=5958118. |
“BMC Remedy Change Management 7.0 User's Guide”—Published Date: Jun. 2006; 410 pages. Available at: http://idbdocs.iadb.org/wsdocs/getdocument.aspx?docnum=35595995. |
Batishchev, Alexander, M. article entitled, “Getting Elevated privileges on Demand Using C#,” published Sep. 9, 2010; 4 pages. Available at: http://www.codeproject.com/KB/vista-security/ElevatedPrivilegesDemand.aspx. |
Chun-Ying Huang et al., Using one-time passwords to prevent password phishing attacks. J Network Computer Applications (2011), doi:10.1016/j.jnca. 2011.02.004. |
Dinei Florencio et al., One-Time Password Access to Any Server without Changing the Server , 11th International conference on Information Security '08, Taipei. Sep. 15, 2008. |
Joseph Bonneau et al., The Quest to Replace Passwords: A Framework for Comparative Evaluation of Web Authentication Schemes, IEEE Symposium on Security and Privacy (SP), 2012, May 20, 2012. |
Lockbox. Printed Nov. 20, 2012. Lockbox: Technology Platform, 3 pgs. http://www.lock-box.com/technology-platform/. |
Stoneware. Printed Nov. 21, 2012. Single Sign-on, 3 pgs. http://www.stone-ware.com/webnetwork/lenovo/sso. |
U.S. Official Action dated Nov. 1, 2012 in U.S. Appl. No. 13/154,660. |
U.S. Official Action dated Jan. 14, 2013 in U.S. Appl. No. 13/301,872. |
U.S. Appl. No. 13/712,688, filed Dec. 12, 2012, entitled “Scalable and Automated Secret Management”. |
Microsoft SQL Server 2008R2 Master Data Services. Printed Date: Oct. 4, 2011. “Master Data Services Environment, Master Data Services Training Guide.” 2010. http://download.microsoft.com/download/5/9/F/59F1639E-EF57-4915-8848-EF1DC2157EBB/02%20MDS%20Environment.pdf. |
IBM. Printed Date: Oct. 4, 2011. “IBM Tivoli Business Continuity Process Manager.” http://www-01.ibm.com/software/tivoli/products/business-continuity-process-mgr/features.html. |
Microsoft TechNet. “Deployment Planning, Architecture, and Guidance on System Center Service Manager.” Published Oct. 2010. http://technet.microsoft.com/en-us/library/gg281359.aspx. |
Travis Wright. “Automating IT: SCSM, SCCM, SCOM, SCVMM, Opalis—Better Together.” Microsoft System, Center Service Manager. Published Aug. 25, 2010. http://blogs.technet.com/b/servicemanager/archive/2010/08/25/automating-it-scsm-sccm-scom-scvmm-opalis-better-together.aspx. |
U.S. Office Action dated Apr. 19, 2013 cited in U.S. Appl. No. 13/413,078. |
U.S. Office Action dated May 2, 2013 cited in U.S. Appl. No. 13/154,660. |
U.S. Final Office Action dated Sep. 24, 2013 cited in U.S. Appl. No. 13/413,078, 46 pgs. |
U.S. Office Action dated Sep. 30, 2013 cited in U.S. Appl. No. 13/154,660. |
U.S. Office Action dated Sep. 30, 2013 cited in U.S. Appl. No. 13/301,872. |
U.S. Office Action dated Jan. 30, 2014 cited in U.S. Appl. No. 13/302,064, 49 pgs. |
U.S. Office Action dated Feb. 24, 2014 cited in U.S. Appl. No. 13/413,078, 44 pgs. |
U.S. Office Action dated Dec. 18, 2013 cited in U.S. Appl. No. 13/712,688. |
U.S. Final Office Action dated Mar. 24, 2014 cited in U.S. Appl. No. 13/154,660, 31 pgs. |
U.S. Office Action dated Apr. 22, 2014 cited in U.S. Appl. No. 13/301,872, 56 pgs. |
U.S. Final Office Action dated Aug. 8, 2014 cited in U.S. Appl. No. 13/413,078, 56 pgs. |
U.S. Final Office Action dated Aug. 27, 2014 cited in U.S. Appl. No. 13/301,872, 55 pgs. |
U.S. Office Action dated Sep. 8, 2014 cited in U.S. Appl. No. 13/154,660, 36 pgs. |
U.S. Office Action dated Dec. 31, 2014 cited in U.S. Appl. No. 13/413,078, 40 pgs. |
U.S. Final Office Action dated Mar. 25, 2015 cited in U.S. Appl. No. 13/154,660, 33 pgs. |
U.S. Office Action dated Jun. 18, 2015 cited in U.S. Appl. No. 13/413,078, 43 pgs. |
U.S. Final Office Action dated Jun. 25, 2015 cited in U.S. Appl. No. 13/301,872, 54 pgs. |
Number | Date | Country | |
---|---|---|---|
20120246703 A1 | Sep 2012 | US |