Single sign-on strategy Sample Clauses

Single sign-on strategy. Single Sign-On (SSO) refers to a user authentication process allowing a user to provide credentials for one (central) application and, once authenticated, get access to a number of other applications (Single Sign-on, 2011). Benefits of SSO include improved user and developer productivity and simplified administration but, on the other hand, a number of problems emerge in systems using SSO; it’s a rather difficult and time consuming approach to be implemented, especially when dealing with applications that have been already implemented. Apart from this drawback, applications using the SSO are vulnerable to attacks, since an intruder takes control of the central application providing the authentication, he may be authorized to access all the other decentralized applications. Moreover, the central authentication system has to be always available in order to avoid denial of services of all the other applications. A number of common SSO approaches are available (List of Single Sign-on Implementations, 2011) including among others configurations based on Kerberos, Smart Card and OTP token approaches. SSO in Dicode As already stated, in the context of Dicode, a number of services will be integrated in the Dicode workbench. Considering that a number of the Dicode services to be integrated require input of user credentials, we plan to use a SSO approach in order to avoid multiple input of user data in all the services (widgets) available via the Dicode workbench. Towards achieving this, a number of REST-based operations have been implemented to facilitate SSO between the Dicode workbench and the collaboration services. A user who wants to get access to the Dicode workbench provides his credentials to the Dicode workbench and once authenticated, the workbench propagates such credentials to the collaboration services by using appropriate REST calls. Figure 3.3 illustrates this process. The REST-based services allow the workbench to perform operations such as “Login”, “Logout”, “Register” new users and “Update Profile” of existing users in the context of the collaboration services. Depending on the progress of the Dicode workbench, additional REST-based services will be provided in the future version of the workbench. Dicode services that require user authentication will use a similar schema when integrated in the workbench, in the near future. REST calls, AESEncryption User Login, Logout Register, Update profile Dicode workbench Login, Logout Register user, Update pr...
Sample 1
AutoNDA by SimpleDocs

Related to Single sign-on strategy

  • Implementation of Strategic Plan Goals This Agreement supports the County’s Strategic Plan, Goal 1, Operational Effectiveness/Fiscal Sustainability. This Agreement will provide revenue reimbursement to the Department for services rendered.

  • Framework Management Structure 2.1.1 The Supplier shall provide a suitably qualified nominated contact (the “Supplier Framework Manager”) who will take overall responsibility for delivering the Goods and/or Services required within this Framework Agreement, as well as a suitably qualified deputy to act in their absence.

  • Joint Network Implementation and Grooming Process Upon request of either Party, the Parties shall jointly develop an implementation and grooming process (the “Joint Grooming Process” or “Joint Process”) which may define and detail, inter alia:

  • Exit Strategy You must have a plan in place to address what will be done in the event of closure or termination of the Services under the Service Agreement. This Exit Strategy may include details on the process that You will employ to cease the Services, arrangements for relevant employees, the continuity of the Services to the Service Users, the handling of records and information in relation to the Services and how the Assets will be dealt with, distributed or transferred. Where the Service Agreement comes to an end for any reason, the Assets (if any) will be distributed as directed by Us. Tasks Activities

  • Completion of Concrete Pours and Emergency Work 24.14.1 Except as provided in this sub-clause an employee shall not work or be required to work in the rain.

  • MANAGEMENT OF EVALUATION OUTCOMES 12.1 The evaluation of the Employee’s performance will form the basis for rewarding outstanding performance or correcting unacceptable performance.

  • Alignment with Modernization Foundational Programs and Foundational Capabilities The activities and services that the LPHA has agreed to deliver under this Program Element align with Foundational Programs and Foundational Capabilities and the public health accountability metrics (if applicable), as follows (see Oregon’s Public Health Modernization Manual, (xxxx://xxx.xxxxxx.xxx/oha/PH/ABOUT/TASKFORCE/Documents/public_health_modernization_man ual.pdf):

  • Erosion Control Structure Maintenance During the period of this contract, Purchaser shall provide maintenance of soil erosion control structures constructed by Purchaser until they become stabilized, but not for more than 1 year after their construction. Contracting Of- ficer may agree to perform such structure maintenance under B4.218, if requested by Purchaser, subject to agreement on rates. Purchaser shall not be responsible for repair of such structures damaged by other National Forest users whose activities are not a part of Pur- chaser’s Operations.

  • Gold Open Access Articles May be shared according to the author-selected end-user license and should contain a CrossMark logo, the end user license, and a DOI link to the formal publication on ScienceDirect. Please refer to Elsevier's posting policy for further information.

  • Commercial Operation Date Testing and Modifications Prior to the Commercial Operation Date, the Connecting Transmission Owner shall test the Connecting Transmission Owner’s Attachment Facilities and System Upgrade Facilities and System Deliverability Upgrades and Developer shall test the Large Generating Facility and the Developer Attachment Facilities to ensure their safe and reliable operation. Similar testing may be required after initial operation. Developer and Connecting Transmission Owner shall each make any modifications to its facilities that are found to be necessary as a result of such testing. Developer shall bear the cost of all such testing and modifications. Developer shall generate test energy at the Large Generating Facility only if it has arranged for the injection of such test energy in accordance with NYISO procedures.

Time is Money Join Law Insider Premium to draft better contracts faster.