DOCSLIB.ORG

Xchangecore Linux Installation Guide

Total Page：16

File Type：pdf, Size：1020Kb

Download full-text PDF Read full-text
Xchangecore Linux Installation Guide www.SpotOnResponse.com XchangeCore Linux Installation Guide July 12, 2014 Ernie Dipko 12 Kiltie Drive Pittsburgh, PA 15235 SpotOnResponse LLC providers of SpotOnResponse™ Location-Based Situational Awareness™ Trusted Crowd-Sourcing™ The XchangeCore Community www.XchangeCore.com www.SpotOnResponse.com Revisions Revision Number Date Description R02C00 03/05/2012 Initial version R02C01 7/12/2014 Transfer to XchangeCore Page 2 2014-12-07 www.SpotOnResponse.com Introduction Purpose SpotOnResponse LLC is pleased to contribute this XchangeCore TechNote to the XchangeCore Community as part of our commitment to expanding the depth and scope of XchangeCore implementation around the world. SpotOnResponse™ is a mobile app and a web application designed to span the needs of emergency management in government and the private sector from the field to the EOC. We are pleased to join the XchangeCore community in this open source effort. This XchangeCore TechNote Linux Installation Guide is provided “as is” with the express request that additions and corrections are requested. Adding the experience of others is encouraged – really is the REASON for the XchangeCore Community. You can submit ideas or improvements for this guide to [email protected]. For further information about SpotOnResponse, please see www.SpotOnResponse.com. Overview This document supplements the XchangeCore Installation Plan which outlines the process to install a XchangeCore core on a Windows® Server. This guide will outline a similar process on a Linux® server. This document is not intended to replace the XchangeCore Installation Plan, and it is highly recommended that the XchangeCore plan be read through before attempting to use this guide. The install documented here was created using a RedHat Linux install on an Amazon EC2 Cloud server, but any Linux release should work. However, there will be fewer changes in the process outlined here on RedHat based Linux. Operating System Setup This procedure will walk through the entire process of configuring an Amazon AMI instance immediately after deployment through to a running XchangeCore core. Setup the Linux Instance The free Amazon Linux instance, known as a T1 Micro Instance, is what we will use for this document. Do not expect this instance to perform under any load. The Micro instances are free and thus slow, with very little memory. They are easily upgraded, though, to a configuration that will support a production XchangeCore. After signing up for an Amazon AWS account, create a new instance using the 64-bit Amazon Linux AMI configuration option. Page 3 2014-12-07 www.SpotOnResponse.com If you choose to utilize this document on an Instance from another cloud provider (Rackspace, GoDaddy, etc.) or on your own Linux install, a basic Linux install is sufficient; the necessary components will be added in the next step. Initial Setup Once the instance is active, follow the provider documentation to connect to the instance via SSH. Once connected, su to root and update the packages using yum (this could take a quite a bit of time on the T1 instance). Install Patches and Required Packages $ su –root {enter password} # yum update When the update completes, it is probably a good idea to restart the instance to make sure there are no initial problems, especially if there was a kernel update in the patches. # shutdown –i6 –g0 –y Where the reboot is complete, connect as root and install the packages we will need to complete the XchangeCore install with the following command: # yum install yum install xterm xorg-x11-utils xorg-x11-fonts-base xorg-x11-fonts-misc \ xorg-x11-font-utils xorg-x11-fonts-Type1 xauth xorg-x11-server-common xclock Allow root To Directly SSH We need to be able to directly connect to the machine as root to complete the eXist install with a GUI. The following command will allow this to happen: # perl -i -pe 's/disable_root: 1/disable_root: 0/' /etc/cloud/cloud.cfg # perl -i -pe 's/#PermitRootLogin .*/PermitRootLogin yes/' /etc/ssh/sshd_config # perl -i -pe 's/.*(ssh-rsa .*)/\1/' /root/.ssh/authorized_keys # /etc/init.d/sshd reload Download and Install the Java JDK We also need to install the Java JDK from Oracle. This is harder than it used to be, because you need an Oracle account (which is free) in order to download the JDK. So the easiest method would be to download the JDK to your PC and then use SCP to transfer it to the XchangeCore server. The JDK can be downloaded from here: http://www.oracle.com/technetwork/java/javase/downloads/index.html Page 4 2014-12-07 www.SpotOnResponse.com I like to install java in /usr and then create a symbolic link to it. For instance, if the download is jdk- 7u13-linux-x64.tar.gz and that is unzipped and untarred in /usr the following directory will be created: /usr/jdk1.7.0_13 Create a symbolic link /usr/java to this directory: # ln –s /usr/jdk1.7.0_13 /usr/java Now when asked for JAVA_HOME, specify the directory /usr/java DNS Configuration DNS entries should be created for the name of the host and also pubsub.<hostname>. It should be noted that often with cloud based servers, private IP address are used on the instances and some network device (Firewall, Load Balancer, or similar) NAT public IP addresses to these non-routable private addresses. This is not a problem, but can be confusing when setting up name services. Add the appropriate public IP address to the DNS records and if necessary, add entries to the local /etc/hosts file for the private IP addresses. For example, your DNS records may look like this: .spotonresponse.com A uicds 166.78.104.149 CNAME pubsub.uicds uicds And the corresponding /etc/hosts file may contain the following entries: 192.168.1.55 uicds.spotonresponse.com pubsub.uicds.spotonresponse.com In this case 166.78.104.149 is the public IP address that points to an interface on the Linux instance that has 192.168.1.55 bound to it. Download and Install XchangeCore To complete the install on a Linux machine, the standard install package will be downloaded and extracted and the XchangeCore-SORlin kit will be downloaded and extracted to the same location. You will need a XchangeCore username and password prior to starting this process. Download the XchangeCore Installation Kit Connect as root and then download the installation packages to Page 5 2014-12-07 www.SpotOnResponse.com # cd / # wget --http-user={USERNAME} --http-password={PASSWORD} https://uicds- test5.saic.com/dist/XchangeCore-InstallKit-1.2.2-64bit-20121001.zip # wget https://app.spotonresponse.com/XchangeCore-SOR-linext.tar Extract the XchangeCore Install and Linux Update # unzip XchangeCore-InstallKit-1.2.2-64bit-20121001.zip # tar xvf XchangeCore-SOR-linext.tar Connect to the Instance to Install To perform the install successfully, an X session will need to be able to use the display on your local machine. This can be a bit tricky if the PC you are on is not set up with an Xserver. You should have already followed the Amazon instructions and have the SSH Key in the appropriate place, imported into PuTTy , or similar. For the examples below, I will use Keypair.pem as the SSH key. OSX install If you are using MAC OSX the process is fairly simple. ssh -i Keypair.pem -X -Y root@{HOST} Windows On Windows, you will need to install Xserver software, here are a few examples: CygwinX: http://x.cygwin.com/ XMing: http://sourceforge.net/projects/xming/ XManager: http://www.netsarang.com/products/xmg_overview.html If you are using PuTTy, when setting up the connection, enter the properties for the connection, under Connection -> SSH -> X11, click Enable X11 forward To test the connection you will be able to forward the X session back to the PC, connect to the server with X11 forwarding enable, and issue the following command: # xclock If the clock does not appear on your desktop, the install of eXist will not be able to complete (which will not allow the tomcat install to complete either). Page 6 2014-12-07 www.SpotOnResponse.com Perform the Install Using the connection that has the X Forwarding session validated, change directories and run the setup process. # cd /XchangeCore/setup/standard64bit # ./setup.ksh You will see the following prompts for information that is necessary for the installation. Be sure to use the Fully Qualified Domain Name that was specified in the DNS configuration. .------------------------ . XchangeCore Setup Beginning .------------------------ .INFO: XchangeCore_HOME=/XchangeCore . .Please enter the following information: Agency Name: SpotOn Response POC Email: [email protected] POC Phone: ###-###-### XchangeCore Server Fully Qualified Domain Name: uicds3.spotonresponse.com XchangeCore System Admin's password: ******** XchangeCore Admin User's password: ******** XchangeCore User's password: ******** The installation will proceed in the following order: OpenDJ will be installed (no download required) eXist will be downloaded and the install will start. Once the install is complete the following screen will come up: Page 7 2014-12-07 www.SpotOnResponse.com In the Password field, enter the password that was specified as the “Admin” users password at the beginning of the install process and click OK. On the next screen, select Tools -> Edit Users Page 8 2014-12-07 www.SpotOnResponse.com Page 9 2014-12-07 www.SpotOnResponse.com Fill out the Username, Passwords, and Home Collection as above, again using the password specified at the beginning of the install. Then click the “Create new Group” icon at the Center Bottom of the dialog box, and create a group named uicds. Then click OK. Verify the screen is populated like the following and then click the “Create User” button. Page 10 2014-12-07 www.SpotOnResponse.com The new user should appear in the dialog box: Page 11 2014-12-07 www.SpotOnResponse.com Close this Window, and verify the initial window now looks like below: Page 12 2014-12-07 www.SpotOnResponse.com Click File -> Quit Page 13 2014-12-07 www.SpotOnResponse.com The eXist install will finish and the database restart.
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]
  • 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 ......................................................................
    [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]