DOCSLIB.ORG

Pliego Prescripciones Técnicas

Total Page：16

File Type：pdf, Size：1020Kb

Download full-text PDF Read full-text
Pliego Prescripciones Técnicas MINISTERIO SUBSECRETARÍA DE HACIENDA Y FUNCIÓN PÚBLICA COMISIONADO PARA EL MERCADO DE TABACOS PLIEGO DE PRESCRIPCIONES TÉCNICAS PARA LA CONTRATACIÓN DE SERVICIOS DE ASISTENCIA TÉCNICA PARA LA ADMINISTRACIÓN Y MANTENIMIENTO DE SISTEMAS INFORMÁTICOS EN EL ÁMBITO DEL COMISIONADO PARA EL MERCADO DE TABACOS Pº HABANA 140 28036 MADRID TEL.: 91 745 72 00 Página 1 de 23 FAX: 91 745 72 12 [email protected] CODIGO DIR 3: E00120903 MINISTERIO SUBSECRETARÍA DE HACIENDA Y FUNCIÓN PÚBLICA COMISIONADO PARA EL MERCADO DE TABACOS 201700000053 I. REQUERIMIENTOS TÉCNICOS ................................................................................................... 3 I.1 .- SEDE DEL COMISIONADO ................................................................................................ 3 I.2 .- ÁMBITO DE APLICACIÓN Y ALCANCE ............................................................................. 3 I.3 .- ESPECIFICACIONES TÉCNICAS DEL CONTRATO .......................................................... 3 II. PRESTACIONES OBLIGATORIAS DEL SERVICIO .................................................................. 10 II.1 .- SERVICIO DE EXPLOTACIÓN ......................................................................................... 10 II.2 .- SERVICIO DE ADMINISTRACIÓN, MANTENIMIENTO Y ACTUALIZACIÓN DE SISTEMAS ...................................................................................................................................... 11 II.3 .- SERVICIOS CON DISPONIBILIDAD 24X7 ....................................................................... 15 II.4 .- SERVICIO DE CENTRO DE ATENCIÓN A USUARIOS Y MICROINFORMÁTICA ........... 17 III. FASES DEL SERVICIO ............................................................................................................. 19 III.1 .- FASE DE ASUNCIÓN DEL SERVICIO ............................................................................. 19 III.2 .- FASE DE EJECUCIÓN DEL SERVICIO ........................................................................... 20 III.3 .- FASE DE DEVOLUCIÓN DEL SERVICIO ........................................................................ 20 IV. HORARIO DE PRESTACIÓN DEL SERVICIO .......................................................................... 21 V. LUGAR DE PRESTACIÓN DEL SERVICIO ............................................................................... 21 VI. METODOLOGÍA EN LA PRESTACIÓN DEL SERVICIO .......................................................... 22 VII. FORMACIÓN DEL PERSONAL TÉCNICO .............................................................................. 22 VIII. TRANSFERENCIA TECNOLÓGICA ....................................................................................... 22 IX. DOCUMENTACIÓN DE LOS TRABAJOS ................................................................................ 22 X. CONFIDENCIALIDAD DE LA INFORMACIÓN .......................................................................... 23 Pº HABANA 140 28036 MADRID TEL.: 91 745 72 00 Página 2 de 23 FAX: 91 745 72 12 [email protected] CODIGO DIR 3: E00120903 MINISTERIO SUBSECRETARÍA DE HACIENDA Y FUNCIÓN PÚBLICA COMISIONADO PARA EL MERCADO DE TABACOS I. REQUERIMIENTOS TÉCNICOS En esta cláusula se especifican los requerimientos técnicos de la contratación. Estas especificaciones abarcan la descripción del entorno físico y lógico en el que se ejecutarán los trabajos. I.1 .- Sede del Comisionado El Comisionado para el Mercado de Tabacos se encuentra situado en el Paseo de la Habana, 140, C.P. 28036, en Madrid. I.2 .- Ámbito de aplicación y alcance El objeto de este contrato comprende las infraestructuras informáticas que proporcionan servicios al Comisionado para el Mercado de Tabacos. Así, el alcance de los trabajos especificados en este pliego engloba las tareas de administración, mantenimiento y actualización de los sistemas informáticos que conforman dicha infraestructura tecnológica. I.3 .- Especificaciones técnicas del contrato El objeto del presente contrato consiste en la prestación de los servicios informáticos de administración, mantenimiento y actualización de los SS.II. que conforman la infraestructura tecnológica del Comisionado. Además, comprende la Atención a Usuarios y el mantenimiento de todo tipo de dispositivos para el tratamiento de la información utilizados por el Comisionado. I.3.1 .- Entorno Tecnológico El entorno tecnológico en que se realizarán los trabajos objeto de este contrato está basado principalmente en las siguientes tecnologías y herramientas. Sistemas operativos - Microsoft Windows Server 2003 SP2 - Microsoft Windows Server 2008 R2 SP1 - Microsoft Windows 7 - Microsoft Windows 10 - Oracle Linux 5 - Oracle Linux 7 - Suse 9 - OpenSUSE versiones 10, 11,12,13 - Debian 8.6 - Centos 7 - Solaris 10 Pº HABANA 140 28036 MADRID TEL.: 91 745 72 00 Página 3 de 23 FAX: 91 745 72 12 [email protected] CODIGO DIR 3: E00120903 MINISTERIO SUBSECRETARÍA DE HACIENDA Y FUNCIÓN PÚBLICA COMISIONADO PARA EL MERCADO DE TABACOS Bases de datos - Oracle MySQL 5.5.20 - MariaDB 10.1.20 en configuración de alta disponibilidad - Microsoft SQL Server 7 - Microsoft Access 97 Correo Electrónico - Qmail, Dovecot - Microsoft Exchange 2010 - Archivado de correo EMC SourceOne Directorio Activo - Microsoft Windows Server 2008 R2 - OpenDJ Virtualización - Oracle VM Manager - VMware - Citrix Monitorización Sistemas - NAGIOS 4 . PNP4Nagios . NagVis . Check_MK Almacenamiento en red - Hardware Sun ZFS Storage 7320 - Switch Sun Blade 6000 NEM 24p 10GbE Servidor Web - Apache 1.3.12 - PHP 4.0.4 Servidor de aplicaciones - Jboss 3.2.3 - Tomcat - WebLogic Sistema de Backup - Zmanda 3.3.9 - HP DataProtector Sistema de atención de Incidencias - Osticket v1.6 ST - OTRS::ITSM 5s Gestión de servicios TIC bajo estándar ITIL - OTRS - Gestión de Incidencias - OTRS - Gestión de Peticiones - OTRS - CMDB - OTRS - Acuerdo de Nivel de Servicio - OTRS - Gestión del Cambio - OTRS - Gestión del Conocimiento Pº HABANA 140 28036 MADRID TEL.: 91 745 72 00 Página 4 de 23 FAX: 91 745 72 12 [email protected] CODIGO DIR 3: E00120903 MINISTERIO SUBSECRETARÍA DE HACIENDA Y FUNCIÓN PÚBLICA COMISIONADO PARA EL MERCADO DE TABACOS I.3.2 .- Entorno Funcional A lo largo del tiempo de duración del contrato el Comisionado podrá evolucionar el entorno tecnológico anteriormente descrito a versiones nuevas de estos u otros productos que sean de su interés, así como determinar la sustitución parcial o total del mismo. Con una antelación no inferior a un mes el Comisionado notificará al adjudicatario los cambios tecnológicos que se van a realizar, facilitando la documentación disponible para el mejor cumplimiento del contrato. I.3.3 .- Entorno Hardware La infraestructura física del Centro de Proceso de Datos (CPD) está ubicada en la 4ª planta de la sede del Comisionado para el Mercado de Tabacos. El CPD está compuesto por: Rack 1 Rack 2 Rack 3 Rack 4 Centralita telefónica A continuación se proporciona una descripción de la infraestructura principal que da soporte al Comisionado: Rack 1 - Chasis Sun Blade 6000 - Servidores blade . Sun X6270 M2 - Arquitectura x86 64-bit (seis unidades) . Sun X6270 M3 - Arquitectura x86 64-bit . Sun SPARC T3-1B - Arquitectura SPARC - Electrónica de red . Sun Blade 6000 ethernet switched NEM 24p 10ge (dos unidades) . HP ProCurve J9022A Switch 2810-48G - Dispositivos NAS . Sun ZFS storage 7320 (dos unidades) - Librería de cintas . SL48 Sun StorageTek - Cabina de almacenamiento . Sun ZFS Storage 7320 con 16TB . Configuración en RAID 1 - Virtualización . Oracle VM Manager Rack 2 - Servidores . ProLiant DL380 G4 (ocho unidades) - Librería de cintas Pº HABANA 140 28036 MADRID TEL.: 91 745 72 00 Página 5 de 23 FAX: 91 745 72 12 [email protected] CODIGO DIR 3: E00120903 MINISTERIO SUBSECRETARÍA DE HACIENDA Y FUNCIÓN PÚBLICA COMISIONADO PARA EL MERCADO DE TABACOS HP StorageWorks MSL5000 Series Library - Electrónica de red . Router Cisco 3600 (dos unidades) . Switch ProCurve J9022A Switch 2810-48G Rack 3 - Electrónica de red . Router Cisco 3800 (dos unidades) . Router Cisco 2600 . Switches HP J9310A Switch E3500yl-24G-PoE+ (dos unidades) . Switch HP ProCurve J9021A Switch 2810-24G . Switches HP ProCurve J9021A Switch 2810-24G (seis unidades) . Firewall StoneGate (dos unidades) Rack 4 o Electrónica de red . Paneles de parcheo . Cableado Centralita telefónica o Modelo HI-COM 300 I.3.4 .- Entorno de Directorio Activo Entorno basado en máquinas virtuales con el sistema operativo Windows Server 2008 R2 que proporciona servicio de directorio al Comisionado, además de interconexión con la plataforma de directorio del Ministerio. Las características más destacables de esta infraestructura son: Infraestructura basada en Windows 2008 R2. Bosque unidominio de directorio activo para la red interna. 150 cuentas de usuario aproximadamente. Relación de confianza con dominios externos al bosque. DNS integrado en DA. I.3.5 .- Entorno de correo electrónico En el momento actual se esta migración el servicio y las cuentas de correo electrónico al ministerio si en el momento comienzo de la ejecución del contrato , quedasen trabajos pendientes de la migración, estos se incluirían en el alcance de la presente licitación. Las características de la infraestructura a sustituir son Qmail 1.2 Máquina Virtual en Oracle Linux 5 Aproximadamente 150 buzones en la plataforma almacenados en local Autenticación con LDAP (OpenDJ) Pº HABANA 140 28036 MADRID TEL.: 91 745 72 00 Página
Load more

Recommended publications
  • MICHAEL STRÖDER Phone +49 721 8304316 [email protected]
    Klauprechtstr. 11 D-76137 Karlsruhe, Germany MICHAEL STRÖDER Phone +49 721 8304316 [email protected] http://www.stroeder.com/ OBJECTIVE A contractor position as a consultant for planning and implementing identity and access management (IAM), security infrastructures (PKI, directory services) and related applications. CAPABILITIES • Planning / designing architectures and implementing mechanisms for secure usage of IT services (PKI, SSL, S/MIME, VPN, LDAP, Identity & Access Management (IAM), Single Sign-On, Firewalls) • Designing, implementing and automatically installing/configuring (DevOps) secure software (e.g. web applications), object-oriented software design and programming (e.g. Python) • System integration and user management in large and complex environments • Training and workshops EXPERIENCE Diverse Projekte (05/2019..12/2020) • Concepts, development, pilots, deployment, integration • Development: Python, migration to Python 3 • Software: OpenLDAP/Æ-DIR, keycloak, integration MS AD • Configuration management: ansible, puppet • Operating systems: Debian Linux, CentOS/RHEL, SLE • Hardening Linux: AppArmor, systemd IT-company Data Science (10/2019..09/2020) • Improved and updated internal IAM based on Æ-DIR (OpenLDAP) • Configuration management with ansible • 3rd-level support for operations As a trainer (05/2019..02/2020) • Python for system administrators • LDAP/OpenLDAP/IAM Versicherung (03/2019) • Implemented secure and highly available configuration of OpenLDAP servers used for customer user accounts • Implemented puppet
    [Show full text]
  • Hosting Requirements Smarter Balanced Assessment Consortium – Test Delivery System
    Hosting Requirements Smarter Balanced Assessment Consortium – Test Delivery System American Institutes for Research Revision History Revision Description Author/Modifier Date Initial Release David Lopez de Quintana October 14, 2013 Updated to latest Amazon Web Service instance types and David Lopez de Quintana March 30, 2014 costs Updated concurrent student numbers, RDS IOP Jeff Treuting (Fairway) May 18, 2016 recommendation and AWS instance types Updated for TDS 3.1.0 Release Jeff Johnson (Fairway) July 10, 2017 Hosting Requirements Smarter Balanced Assessment Consortium Test Delivery System Contents Purpose ......................................................................................................................................................... 4 System Overview .......................................................................................................................................... 4 Component Software ................................................................................................................................... 6 Development/Operation Software Packages 6 Software Packages by Component 7 Deployment Assumptions .......................................................................................................................... 10 Deployment Configurations ....................................................................................................................... 10 Test Delivery Unit 11 Elastic Load Balancer 13 Web Server Instance Type 13 AWS ElastiCache – Redis Cluster
    [Show full text]
  • Opendj Installation Guide Version 2.6
    OpenDJ Installation Guide Version 2.6 Mark Craig ForgeRock AS 201 Mission St., Suite 2900 San Francisco, CA 94105, USA +1 415-599-1100 (US) www.forgerock.com Copyright © 2011-2016 ForgeRock AS. Abstract This guide shows you how to install OpenDJ directory services. The OpenDJ project offers open source LDAP directory services in Java. This work is licensed under the Creative Commons Attribution-NonCommercial-NoDerivs 3.0 Unported License. To view a copy of this license, visit http://creativecommons.org/licenses/by-nc-nd/3.0/ or send a letter to Creative Commons, 444 Castro Street, Suite 900, Mountain View, California, 94041, USA. ForgeRock™ is the trademark of ForgeRock Inc. or its subsidiaries in the U.S. and in other countries. Trademarks are the property of their respective owners. UNLESS OTHERWISE MUTUALLY AGREED BY THE PARTIES IN WRITING, LICENSOR OFFERS THE WORK AS-IS AND MAKES NO REPRESENTATIONS OR WARRANTIES OF ANY KIND CONCERNING THE WORK, EXPRESS, IMPLIED, STATUTORY OR OTHERWISE, INCLUDING, WITHOUT LIMITATION, WARRANTIES OF TITLE, MERCHANTIBILITY, FITNESS FOR A PARTICULAR PURPOSE, NONINFRINGEMENT, OR THE ABSENCE OF LATENT OR OTHER DEFECTS, ACCURACY, OR THE PRESENCE OF ABSENCE OF ERRORS, WHETHER OR NOT DISCOVERABLE. SOME JURISDICTIONS DO NOT ALLOW THE EXCLUSION OF IMPLIED WARRANTIES, SO SUCH EXCLUSION MAY NOT APPLY TO YOU. EXCEPT TO THE EXTENT REQUIRED BY APPLICABLE LAW, IN NO EVENT WILL LICENSOR BE LIABLE TO YOU ON ANY LEGAL THEORY FOR ANY SPECIAL, INCIDENTAL, CONSEQUENTIAL, PUNITIVE OR EXEMPLARY DAMAGES ARISING OUT OF THIS LICENSE OR THE USE OF THE WORK, EVEN IF LICENSOR HAS BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGES.
    [Show full text]
  • Distributed Data Framework Architecture
    Distributed Data Framework Architecture Version 2.26.17. Copyright (c) Codice Foundation Table of Contents License. 1 1. Catalog Framework API . 2 2. Catalog API Design . 4 2.1. Ensuring Compatibility . 4 2.2. Catalog Framework Sequence Diagrams . 4 2.2.1. Error Handling. 5 2.2.2. Query . 5 2.2.3. Product Caching. 6 2.2.4. Product Download Status . 7 2.2.5. Catalog API . 7 2.2.5.1. Catalog API Search Interfaces. 7 2.2.5.2. Catalog Search Result Objects. 7 2.2.5.3. Search Programmatic Flow . 8 2.2.5.4. Sort Policies. 8 2.2.5.5. Product Retrieval . 9 2.2.5.6. Notifications and Activities . 10 2.3. Included Catalog Frameworks, Associated Components, and Configurations. 10 2.3.1. Standard Catalog Framework . 10 2.3.1.1. Installing the Standard Catalog Framework. 11 2.3.1.2. Configuring the Standard Catalog Framework . 11 2.3.1.3. Known Issues with Standard Catalog Framework . 12 2.3.2. Catalog Framework Camel Component . 12 2.3.2.1. Sending Messages to Catalog Framework Endpoint . 12 3. Transformers. 13 3.1. Available Input Transformers . 15 3.2. Available Metacard Transformers . 16 3.3. Available Query Response Transformers . 16 3.4. Transformers Details . 17 3.4.1. Atom Query Response Transformer . 17 3.4.1.1. Installing the Atom Query Response Transformer . 17 3.4.1.2. Configuring the Atom Query Response Transformer . 17 3.4.1.3. Using the Atom Query Response Transformer. 17 3.4.2. CSW Query Response Transformer . 21 3.4.2.1.
    [Show full text]
  • Advanced Authentication 6.3 Administration Guide
    Advanced Authentication 6.3 Administration Guide December 2019 Legal Notice For information about legal notices, trademarks, disclaimers, warranties, export and other use restrictions, U.S. Government rights, patent policy, and FIPS compliance, see http://www.microfocus.com/about/legal/. © Copyright 2021 Micro Focus or one of its affiliates. 2 Contents About this Book 15 1 Introduction to Advanced Authentication 17 1.1 How Is Advanced Authentication Better Than Other Solutions. .17 1.2 Key Features. .17 1.3 Advanced Authentication Server Components . .18 1.3.1 Administration Portal . .19 1.3.2 Self-Service Portal. .19 1.3.3 Helpdesk Portal. .20 1.3.4 Reporting Portal . .20 1.4 Architecture . .20 1.4.1 Basic Architecture. .20 1.4.2 Enterprise Level Architecture . .21 1.4.3 Enterprise Architecture With A Load Balancer. .23 1.5 Terminologies. .24 1.5.1 Authentication Method . .24 1.5.2 Authentication Chain . .24 1.5.3 Authentication Event . .24 1.5.4 Endpoint . .24 Part I Configuring Advanced Authentication 25 2 Logging In to the Advanced Authentication Administration Portal27 3 End to End Configuration with Examples 29 3.1 Implementing Multi-Factor Authentication to VPN . .29 3.1.1 Prerequisites . .30 3.1.2 Considerations Before Configuration . 30 3.1.3 Add a Repository. .31 3.1.4 Configure Methods. .32 3.1.5 Create a Chain. .32 3.1.6 Configure Public External URLs Policy. .32 3.1.7 Assign Chain to RADIUS Server Event . 33 3.1.8 Configure the OpenVPN Server . .33 3.1.9 End User Tasks . .34 3.2 Securing Windows Workstation with Multi-Factor Authentication.
    [Show full text]
  • RFP Announcement
    RFP Announcement National Association of State Workforce Agencies (NASWA) Center for Employment Security Education and Research (CESER) Information Technology Support Center (ITSC) Request for Proposal: Unemployment Insurance/Workforce System Connectivity Project: Integrated Workforce Registration (IWR) System The National Association of State Workforce Agencies (NASWA) and Information Technology Support Center (ITSC)NASWA and the ITSC are seeking to procure the services of a contractor through a firm fixed price contract to develop and implement a fully integrated Unemployment Insurance (UI)/ Employment Services (ES)/ Workforce Investment Act (WIA) Integrated Workforce Registration System(IWR). The IWR system will become the point of entry into the state system for unemployed individuals/jobseekers in the three pilot states (Mississippi, Oregon and New York) that have partnered with NASWA/ITSC for this project. The technology solution is required to be built using open source technologies. The development effort will be overseen by ITSC, in partnership with the three pilot states and the United States Department of Labor (USDOL), Employment and Training Administration (ETA). The RFP consists of the following documents: RFP: Unemployment Insurance/Workforce System Connectivity Project: Integrated Workforce Registration System Appendix A: NASWA Actual “To-Be” Processes and Use Cases Appendix B: Data Model with Data Flow Mapping Appendix C: Registration Data Flow Appendix D: Connectivity Reference System Architecture Appendix E: IWR System Requirements Appendix F: CESER General Terms and Conditions Appendix G: A National Call For Innovation Appendix H: Profile Page Description Appendix I: ITSC Project Management Template Appendix J: ITSC Project Schedule Template Important Dates: RFP Publication Date: September 25, 2012 Bidders Webinar/Teleconference: October 5, 2012; 1:00 PM EDT - http://naswa.webex.com - Keyword Search: “RFP” - Click “Register” Proposal Due Date: October 26, 2012, by 5:00 p.m.
    [Show full text]
  • TDS Deployment Evaluation
    TDS Deployment Evaluation Prepared for: SMARTER BALANCED Fairway Technologies, Inc. April 27, 2016 Fairway Technologies © Copyright 2012 Fairway Technologies, Inc. All rights reserved. Proprietary and Confidential TDS Deployment Evaluation 2 Table of Contents Executive Summary ....................................................................................................... 3 Build Process ............................................................................................................... 3 Master Build Sequence ................................................................................................. 3 Unit Tests ................................................................................................................ 3 Maven Settings .......................................................................................................... 3 Deployment Process ....................................................................................................... 5 Overall .................................................................................................................... 5 Application Deployment and Configuration ......................................................................... 11 Shared Services ....................................................................................................... 11 Assessment Delivery Components .................................................................................. 17 Assessment Scoring ..................................................................................................
    [Show full text]
  • Integrating LDAP with Payara® Server
    User Guide Integrating LDAP with Payara® Server The Payara® Platform - Production-Ready, Cloud Native and Aggressively Compatible. Integrating LDAP with Payara® Server Contents Starting the LDAP Server 1 Configuring Security 5 Creating a Web Application 6 Extracting User Information 11 Seamless Authentication and Authorization 17 About Payara Services, Ltd 18 Integrating LDAP with Payara® Server If you work in an organization with a robust IT department, it’s very likely that you are using a LDAP server to handle your user directory information. You probably have to follow some general guidelines dictating that all web applications deployed within the organization’s infrastructure must access this user directory; and must authenticate and authorize the users that will interact with them. This is a very common scenario nowadays. In this guide, I will illustrate the implementation of the LDAP integration using a sample scenario: integrate Payara® Server with a LDAP user directory and manage the authentication and authorization of a sample web application. Starting the LDAP Server There are many different LDAP server implementations in the market today (in both commercial and open source models). For our scenario, we will quickly start an OpenDJ instance using a Docker container and set up a directory domain with some test users and groups. First, we start with a new Docker image that will download the OpenDJ binaries and run them in a container. This is a Java based image, since OpenDJ needs the JDK to run: FROM java:8 MAINTAINER Fabio Turizo <[email protected]> WORKDIR /opt ENV JAVA_HOME /usr/lib/jvm/java-8-openjdk-amd64/ ENV MVN_REPO=https://maven.forgerock.org/repo/repo/org/forgerock/opendj ENV OPENDJ_VERSION=3.0.0 ENV SERVER_PATH opendj-server-legacy RUN curl $MVN_REPO/$SERVER_PATH/$OPENDJ_VERSION/$SERVER_PATH $OPENDJ_VERSION.
    [Show full text]
  • Nexentastor 4.0.4 User Guide
    NexentaStor User Guide 4.0.4 Date: June, 2015 Subject: NexentaStor User Guide Software: NexentaStor Software Version: 4.0.4 Part Number: 3000-nxs-4.0.4 000057-B Copyright © 2015 Nexenta Systems, ALL RIGHTS RESERVED www.nexenta.com NexentaStor User Guide Copyright © 2015 Nexenta SystemsTM, ALL RIGHTS RESERVED Notice: No part of this publication may be reproduced or transmitted in any form or by any means, electronic or mechanical, including photocopying and recording, or stored in a database or retrieval system for any purpose, without the express written permission of Nexenta Systems (hereinafter referred to as “Nexenta”). Nexenta reserves the right to make changes to this document at any time without notice and assumes no responsibility for its use. Nexenta products and services only can be ordered under the terms and conditions of Nexenta Systems’ applicable agreements. All of the features described in this document may not be available currently. Refer to the latest product announcement or contact your local Nexenta Systems sales office for information on feature and product availability. This document includes the latest information available at the time of publication. Nexenta, NexentaStor, NexentaEdge, and NexentaConnect are registered trademarks of Nexenta Systems in the United States and other countries. All other trademarks, service marks, and company names in this document are properties of their respective owners. Product Versions Applicable to this Documentation: Product Versions supported NexentaStorTM 4.0.4 Copyright © 2015 Nexenta Systems, ALL RIGHTS RESERVED ii www.nexenta.com NexentaStor User Guide Contents Preface . xv 1 Introduction . .1 About NexentaStor . .1 About NexentaStor Components . .2 Using Plugins .
    [Show full text]
  • Release Notes / Forgerock Identity Management 7
    Release Notes / ForgeRock Identity Management 7 Latest update: 7.0.2 ForgeRock AS. 201 Mission St., Suite 2900 San Francisco, CA 94105, USA +1 415-599-1100 (US) www.forgerock.com Copyright © 2011-2021 ForgeRock AS. Abstract Notes covering ForgeRock® Identity Management software requirements, fixes, and known issues. This software offers flexible services for automating management of the identity life cycle. This work is licensed under the Creative Commons Attribution-NonCommercial-NoDerivs 3.0 Unported License. To view a copy of this license, visit https://creativecommons.org/licenses/by-nc-nd/3.0/ or send a letter to Creative Commons, 444 Castro Street, Suite 900, Mountain View, California, 94041, USA. ForgeRock® and ForgeRock Identity Platform™ are trademarks of ForgeRock Inc. or its subsidiaries in the U.S. and in other countries. Trademarks are the property of their respective owners. UNLESS OTHERWISE MUTUALLY AGREED BY THE PARTIES IN WRITING, LICENSOR OFFERS THE WORK AS-IS AND MAKES NO REPRESENTATIONS OR WARRANTIES OF ANY KIND CONCERNING THE WORK, EXPRESS, IMPLIED, STATUTORY OR OTHERWISE, INCLUDING, WITHOUT LIMITATION, WARRANTIES OF TITLE, MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE, NONINFRINGEMENT, OR THE ABSENCE OF LATENT OR OTHER DEFECTS, ACCURACY, OR THE PRESENCE OF ABSENCE OF ERRORS, WHETHER OR NOT DISCOVERABLE. SOME JURISDICTIONS DO NOT ALLOW THE EXCLUSION OF IMPLIED WARRANTIES, SO SUCH EXCLUSION MAY NOT APPLY TO YOU. EXCEPT TO THE EXTENT REQUIRED BY APPLICABLE LAW, IN NO EVENT WILL LICENSOR BE LIABLE TO YOU ON ANY LEGAL THEORY FOR ANY SPECIAL, INCIDENTAL, CONSEQUENTIAL, PUNITIVE OR EXEMPLARY DAMAGES ARISING OUT OF THIS LICENSE OR THE USE OF THE WORK, EVEN IF LICENSOR HAS BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGES.
    [Show full text]
  • Mobile Application Single Sign-On Improving Authentication for Public Safety First Responders
    DRAFT NIST SPECIAL PUBLICATION 1800-13C Mobile Application Single Sign-On Improving Authentication for Public Safety First Responders Volume C: How-To Guides Paul Grassi Applied Cybersecurity Division Information Technology Laboratory Bill Fisher National Cybersecurity Center of Excellence Information Technology Laboratory Santos Jha William Kim Taylor McCorkill Joseph Portner Mark Russell Sudhi Umarji The MITRE Corporation McLean, VA April 2018 DRAFT This publication is available free of charge from: https://www.nccoe.nist.gov/projects/use-cases/mobile-sso DRAFT DISCLAIMER Certain commercial entities, equipment, products, or materials may be identified in this document in order to describe an experimental procedure or concept adequately. Such identification is not intended to imply recommendation or endorsement by NIST or NCCoE, nor is it intended to imply that the entities, equipment, products, or materials are necessarily the best available for the purpose. National Institute of Standards and Technology Special Publication 1800-13C, Natl. Inst. Stand. Technol. Spec. Publ. 1800-13C, 163 pages, (April 2018), CODEN: NSPUE2 FEEDBACK You can improve this guide by contributing feedback. As you review and adopt this solution for your own organization, we ask you and your colleagues to share your experience and advice with us. Comments on this publication may be submitted to: [email protected]. Public comment period: April 16, 2018 through June 18, 2018 All comments are subject to release under the Freedom of Information Act (FOIA). National
    [Show full text]
  • Oracle® Identity Manager Connector Guide for IBM RACF Advanced
    Oracle® Identity Manager Connector Guide for IBM RACF Advanced Release 9.1.0.9.0 F21285-10 Aug 2021 Oracle Identity Manager Connector Guide for IBM RACF Advanced, Release 9.1.0.9.0 F21285-10 Copyright © 2019, 2021, Oracle and/or its affiliates. Primary Author: Debapriya Datta Contributing Authors: Maya Chakrapani, Mike Howlett Contributors: Amol Datar, Shradha Joshi, Vaidyanath Laturkar, Nilesh Nikalje This software and related documentation are provided under a license agreement containing restrictions on use and disclosure and are protected by intellectual property laws. Except as expressly permitted in your license agreement or allowed by law, you may not use, copy, reproduce, translate, broadcast, modify, license, transmit, distribute, exhibit, perform, publish, or display any part, in any form, or by any means. Reverse engineering, disassembly, or decompilation of this software, unless required by law for interoperability, is prohibited. The information contained herein is subject to change without notice and is not warranted to be error-free. If you find any errors, please report them to us in writing. If this is software or related documentation that is delivered to the U.S. Government or anyone licensing it on behalf of the U.S. Government, then the following notice is applicable: U.S. GOVERNMENT END USERS: Oracle programs (including any operating system, integrated software, any programs embedded, installed or activated on delivered hardware, and modifications of such programs) and Oracle computer documentation or other Oracle data delivered to or accessed by U.S. Government end users are "commercial computer software" or "commercial computer software documentation" pursuant to the applicable Federal Acquisition Regulation and agency-specific supplemental regulations.
    [Show full text]