DOCSLIB.ORG

Jamf Pro Overview—Macos Smart Card Functionality

Total Page：16

File Type：pdf, Size：1020Kb

Download full-text PDF Read full-text

Load more

Jamf Pro Overview macOS Smart card Functionality Page 1 of 26 Jamf Pro Overview 1 Overview 6 History 7 Mac OS X 10.6 and below 7 Mac OS X 10.7 - 10.12 7 Mac OS X Sierra 10.12 - macOS High Sierra 10.13 7 Mac OS X Sierra 10.12.0-10.12.4 7 Mac OS X Sierra 10.12.4 - macOS High Sierra 10.13.1 7 macOS High Sierra 10.13.2 8 macOS High Sierra 10.13.4 8 macOS Mojave 10.14.0 - 10.14.6 8 macOS Mojave 10.14.6 8 macOS Catalina 10.15.0 9 Pre-10.12 Support 10 Additional USB Drivers 10 FileVault 11 Basic Setup 11 Advanced Setup 11 Active Directory 12 Native Support for AD bound Macs 12 Local User Account - Attribute Mapping 12 Mobile User Account - Attribute Mapping 12 Advanced Integration 13 Configuration Profile 14 Note 15 Jamf Pro 10.3 15 Enforce Smart card 16 Verify Smart card Certificate 16 Jamf Pro 10.12 16 Mandatory use of Smart cards 17 1. Device Enrollment 17 Page 2 of 26 2. Enforce FileVault 17 3. Set up a FileVault User 17 4. Smart card Pairing 17 Non-Directory Services 17 Active Directory 17 5. Configuration Profile 18 6. Terminal Commands 18 Alternative Distribution 19 Scripts 20 Enforce ‘sudo’ to use Smart card 20 Enforce ‘su’ to use Smart card 20 Enforce ‘login’ to use Smart card 20 Enforce Screensaver to activate on removal of Smart card 20 Active Directory Attribute Mapping 21 Extension Attributes 22 Validate Smart card Pairing is enabled 22 Review if a Smart card is in User’s Keychain 22 Display Smart card enabled user 22 Smart card Logging 22 Review Screensaver Setting for Smart card Removal 22 Review if ‘login’ command has been protected with Smart card Authentication 23 Review if ‘sudo’ command has been protected with Smart card Authentication 23 Review if ‘su’ command has been protected with Smart card Authentication 23 Troubleshooting 24 Validate Smart card Pairing is enabled 24 Review if a Smart card is in User’s Keychain 24 Smart card Logging 24 Review the hash for Smart card enabled user 24 Smart card Manual 24 Smart card Diagnostic 24 System-wide Diagnostic Report 25 PAM Module 25 Page 3 of 26 Review current Login Window Settings 25 Smart card Information from System Profiler 25 Review the list of Smart cards 25 References 26 Apple Documentation 26 TokenD 26 CryptoTokenKit 26 MDM Reference 26 PIV Mandatory 26 Page 4 of 26 © 2018 Jamf. All rights reserved. Jamf has made all efforts to ensure that this guide is accurate. Jamf 100 Washington Ave S Suite 1100 Minneapolis, MN 55401-2155 (612) 605-6625 Apple, the Apple logo, macOS, Mac OS X, macOS High Sierra 10.13, macOS Sierra 10.12, CryptoTokenKit, FileVault, are trademarks of Apple Inc., registered in the United States and other countries. App Store is a service mark of Apple Inc., registered in the United States and other countries. Jamf Pro, Jamf, the Jamf Logo, are registered or common law trademarks of JAMF SOFTWARE, LLC in the U.S. and other countries. All other product and service names mentioned herein are either registered trademarks or trademarks of their respective companies. Page 5 of 26 Overview With user-friendly and easy to use products, along with an ever-expanding ecosystem of apps and resources, it’s no surprise that Apple continues to make substantial strides in enterprise settings around the world. Apple devices all come with built-in security features that make them a logical choice for any security-conscious organization. However, government and financial sectors often need more than what Apple offers out of the box. To accommodate these organizations, Smart cards can be leveraged as an extra layer of security authentication on Mac. In this white paper, we explain the history of Smart card usage with Apple and provide guidance to Jamf customers on the best methods for managing and reporting on Smart cards, like Personal Identity Verification (PIV) or Common Access Card - Next Gen (CAC-NG*), for Apple devices. You’ll learn how to: • Deploy tools like Centrify and ADmitMac PKI that contain drivers for reading Smart cards on older macOS devices • Leverage macOS built in CryptoTokenKit • Create local user accounts to support Smart cards • Support Active Directory binding natively or through additional tools • Create configuration profiles to centrally manage and enforce Smart card services • Leverage extension attributes to report on various Mac settings, including Smart cards • Troubleshoot steps if an issue should arise * CAC-NG card specification requires the card include a PIV credential This document will focus most attention on macOS High Sierra 10.13 and the Jamf Pro management solution. You should have advanced knowledge of how to use Jamf Pro in secure environments. Page 6 of 26 History Smart card support within macOS has changed over the years. Here is a record of what type of support Apple has built into each version of macOS. (Note: Most data related to this section was obtained on Cem Pava’s blog. [See References] ) Mac OS X 10.6 and below Mac OS X systems used to contain a low level module service called ‘tokend’. This service allowed native reading of certain Smart cards (1): 1. BELPIC.Tokend: Belgian National ID (BELPIC) compliant Smart cards 2. CAC.Tokend: Common Access Card (CAC) compliant Smart cards 3. JPKI.Tokend: japanese PKI (JPKI) compliant Smart cards 4. PIV.Tokend: Personal Identity Verification (PIV) compliant Smart cards 5. tokendPKCS11.so: PKCS-11 shim over TokenD (Mac OS X 10.6 only) Mac OS X 10.7 - 10.12 Smart card services with TokenD were removed from Mac OS X and moved into an open source platform. This is placed within Apple’s macOS forge site: https://www.macosforge.org Smart card Services specifically at: https://smartcardservices.github.io Customers could utilize third-party applications and drivers to support Smart cards. Centrify and ADmitMac are two primary solutions that offer support. Mac OS X Sierra 10.12 - macOS High Sierra 10.13 Apple transitioned to native support of Smart cards using CryptoTokenKit (CTK) with new management functionalities through mobile device management (MDM). More information can be found in Terminal with the ‘man SmartCardServices’ command. Legacy Smart card services using TokenD (CDSA) are still supported in Sierra and High Sierra using the GitHub project: https://smartcardservices.github.io Mac OS X Sierra 10.12.0-10.12.4 Apple built-in CTK supported Smart cards natively with command-line interface management. This can be reviewed by using “man SmartCardServices” and “man sc_auth” in Terminal. Mac OS X Sierra 10.12.4 - macOS High Sierra 10.13.1 Page 7 of 26 Apple began adding MDM Configuration Profile settings to centrally manage some components of the Smart card functionality. These included: 1. Allow Smart card 2. Only allow one Smart card per user 3. Allow user pairing 4. Verify the certificate is trusted - boolean on or off macOS High Sierra 10.13.2 A mandatory enforcement of Smart card usage was introduced to meet the US Government requirements, known as PIV-M or mandatory use of PIV credentials. This is a response to Homeland Security Presidential Directive - 12. [See References] This setting enforces Smart card on macOS functions. Terminal related functions (i.e. ‘sudo’, ‘login’, ‘su’, etc.) can be set up with Smart card mandatory authentication using settings from Page 15. This does not allow a per-user management of Smart cards. The following MDM configuration profile setting was introduced to support PIV-M. 1. Force Smart card authentication on all users Apple changed the MDM Configuration Profile key that controls the certificate trust check behavior, adding two additional options for check revocation (soft) and check revocation (hard). Soft requires the device to check revocation upon network connectivity to OCSP/CRL, whereas Hard validates revocation immediately against OCSP/CRL. 1. Check Certificate Trust (with soft revocation check) 2. Check Certificate Trust (with hard revocation check) macOS High Sierra 10.13.4 Apple added new management functionality to allow the local administrator to change the Smart card PIN using ‘sc_auth’. macOS Mojave 10.14.0 - 10.14.6 Apple added new management functionality for configuration profiles to enforce the “Lock screensaver on Smart card removal” macOS Mojave 10.14.6 Take a hash of the domain of your certificate, allowing you to identify only certain domains can pair and authenticate. PCSC bug fixes Page 8 of 26 macOS Catalina 10.15.0 Apple added updates to the “man SmartCardServices” in referencing various Smart card functionality to CTK. These include: Identity Picker - Ability to choose which identity needs to be used for authentication. User based Enforcement - No longer tied to device based enforcement. Allow login for unpair user. Ability to relax mandatory Smart card policy for an identified group of users. Allowed to make a local user group or directory based group that is allowed to bypass the Smart card mandatory (PIV-M) policy. Certificate pinning - Ability to restrict Smart card login to cards issued from specific domains TokenD is now dead. Page 9 of 26 Pre-10.12 Support Jamf Pro can assist any customer in deploying tools like Centrify and ADmitMac PKI that contain drivers for reading Smart cards in systems prior to Mac OS X 10.12. Additional USB Drivers Apple has built in support for a very wide range of PIV and CAC-NG Smart cards, therefore, the need to build any additional drivers would be rare. If you have a need to build an additional Smart card driver please review Apple’s man page for Smart card Services: OS X (macOS) has built-in support for USB CCID class-compliant Smart card readers.
Recommended publications
  • A Microkernel API for Fine-Grained Decomposition

    A Microkernel API for Fine-Grained Decomposition

    A Microkernel API for Fine-Grained Decomposition Sebastian Reichelt Jan Stoess Frank Bellosa System Architecture Group, University of Karlsruhe, Germany freichelt,stoess,[email protected] ABSTRACT from the microkernel APIs in existence. The need, for in- Microkernel-based operating systems typically require spe- stance, to explicitly pass messages between servers, or the cial attention to issues that otherwise arise only in dis- need to set up threads and address spaces in every server for tributed systems. The resulting extra code degrades per- parallelism or protection require OS developers to adopt the formance and increases development effort, severely limiting mindset of a distributed-system programmer rather than to decomposition granularity. take advantage of their knowledge on traditional OS design. We present a new microkernel design that enables OS devel- Distributed-system paradigms, though well-understood and opers to decompose systems into very fine-grained servers. suited for physically (and, thus, coarsely) partitioned sys- We avoid the typical obstacles by defining servers as light- tems, present obstacles to the fine-grained decomposition weight, passive objects. We replace complex IPC mecha- required to exploit the benefits of microkernels: First, a nisms by a simple function-call approach, and our passive, lot of development effort must be spent into matching the module-like server model obviates the need to create threads OS structure to the architecture of the selected microkernel, in every server. Server code is compiled into small self- which also hinders porting existing code from monolithic sys- contained files, which can be loaded into the same address tems. Second, the more servers exist | a desired property space (for speed) or different address spaces (for safety).
  • Openvms Record Management Services Reference Manual

    Openvms Record Management Services Reference Manual

    OpenVMS Record Management Services Reference Manual Order Number: AA-PV6RD-TK April 2001 This reference manual contains general information intended for use in any OpenVMS programming language, as well as specific information on writing programs that use OpenVMS Record Management Services (OpenVMS RMS). Revision/Update Information: This manual supersedes the OpenVMS Record Management Services Reference Manual, OpenVMS Alpha Version 7.2 and OpenVMS VAX Version 7.2 Software Version: OpenVMS Alpha Version 7.3 OpenVMS VAX Version 7.3 Compaq Computer Corporation Houston, Texas © 2001 Compaq Computer Corporation Compaq, AlphaServer, VAX, VMS, the Compaq logo Registered in U.S. Patent and Trademark Office. Alpha, PATHWORKS, DECnet, DEC, and OpenVMS are trademarks of Compaq Information Technologies Group, L.P. in the United States and other countries. UNIX and X/Open are trademarks of The Open Group in the United States and other countries. All other product names mentioned herein may be the trademarks of their respective companies. Confidential computer software. Valid license from Compaq required for possession, use, or copying. Consistent with FAR 12.211 and 12.212, Commercial Computer Software, Computer Software Documentation, and Technical Data for Commercial Items are licensed to the U.S. Government under vendor’s standard commercial license. Compaq shall not be liable for technical or editorial errors or omissions contained herein. The information in this document is provided "as is" without warranty of any kind and is subject to change without notice. The warranties for Compaq products are set forth in the express limited warranty statements accompanying such products. Nothing herein should be construed as constituting an additional warranty.
  • 706 What's New in Security 07 FINAL.Key

    706 What's New in Security 07 FINAL.Key

    System Frameworks #WWDC16 What’s New in Security Session 706 Lucia Ballard Secure Transports Engineering Manager Simon Cooper Trusted Execution Engineering Manager © 2016 Apple Inc. All rights reserved. Redistribution or public display not permitted without written permission from Apple. What’s New in Security? What’s New in Security? Network Security What’s New in Security? Network Security Cryptography APIs What’s New in Security? Network Security Cryptography APIs Platform Security on macOS What’s New in Network Security Lucia Ballard Secure Transports Engineering Manager Secure Communications Secure Communications HTTPS is the new HTTP • Confidentiality • Data integrity Secure Communications HTTPS is the new HTTP • Confidentiality • Data integrity Not all HTTPS is created equal App Transport Security Current standards App Transport Security Current standards For NSURLSession and NSURLConnection APIs App Transport Security Current standards For NSURLSession and NSURLConnection APIs • TLS v1.2 App Transport Security Current standards For NSURLSession and NSURLConnection APIs • TLS v1.2 • Strong crypto—AES-128 and SHA-2 App Transport Security Current standards For NSURLSession and NSURLConnection APIs • TLS v1.2 • Strong crypto—AES-128 and SHA-2 • Forward secrecy—ECDHE App Transport Security Current standards For NSURLSession and NSURLConnection APIs • TLS v1.2 • Strong crypto—AES-128 and SHA-2 • Forward secrecy—ECDHE Exceptions—global or for particular domains App Transport Security Enforcement App Transport Security Enforcement Enforced
  • Introduction to Unix

    Introduction to Unix

    Introduction to Unix Rob Funk <[email protected]> University Technology Services Workstation Support http://wks.uts.ohio-state.edu/ University Technology Services Course Objectives • basic background in Unix structure • knowledge of getting started • directory navigation and control • file maintenance and display commands • shells • Unix features • text processing University Technology Services Course Objectives Useful commands • working with files • system resources • printing • vi editor University Technology Services In the Introduction to UNIX document 3 • shell programming • Unix command summary tables • short Unix bibliography (also see web site) We will not, however, be covering these topics in the lecture. Numbers on slides indicate page number in book. University Technology Services History of Unix 7–8 1960s multics project (MIT, GE, AT&T) 1970s AT&T Bell Labs 1970s/80s UC Berkeley 1980s DOS imitated many Unix ideas Commercial Unix fragmentation GNU Project 1990s Linux now Unix is widespread and available from many sources, both free and commercial University Technology Services Unix Systems 7–8 SunOS/Solaris Sun Microsystems Digital Unix (Tru64) Digital/Compaq HP-UX Hewlett Packard Irix SGI UNICOS Cray NetBSD, FreeBSD UC Berkeley / the Net Linux Linus Torvalds / the Net University Technology Services Unix Philosophy • Multiuser / Multitasking • Toolbox approach • Flexibility / Freedom • Conciseness • Everything is a file • File system has places, processes have life • Designed by programmers for programmers University Technology Services
  • Intelligent OS X Malware Threat Detection with Code Inspection

    Intelligent OS X Malware Threat Detection with Code Inspection

    This is a repository copy of Intelligent OS X malware threat detection with code inspection. White Rose Research Online URL for this paper: http://eprints.whiterose.ac.uk/128371/ Version: Published Version Article: Pajouh, H.H., Dehghantanha, A. orcid.org/0000-0002-9294-7554, Khayami, R. et al. (1 more author) (2018) Intelligent OS X malware threat detection with code inspection. Journal of Computer Virology and Hacking Techniques, 14 (3). pp. 213-223. ISSN 2274-2042 https://doi.org/10.1007/s11416-017-0307-5 Reuse This article is distributed under the terms of the Creative Commons Attribution (CC BY) licence. This licence allows you to distribute, remix, tweak, and build upon the work, even commercially, as long as you credit the authors for the original work. More information and the full terms of the licence here: https://creativecommons.org/licenses/ Takedown If you consider content in White Rose Research Online to be in breach of UK law, please notify us by emailing [email protected] including the URL of the record and the reason for the withdrawal request. [email protected] https://eprints.whiterose.ac.uk/ J Comput Virol Hack Tech DOI 10.1007/s11416-017-0307-5 ORIGINAL PAPER Intelligent OS X malware threat detection with code inspection Hamed Haddad Pajouh1 · Ali Dehghantanha2 · Raouf Khayami1 · Kim-Kwang Raymond Choo3,4 Received: 31 July 2017 / Accepted: 27 September 2017 © The Author(s) 2017. This article is an open access publication Abstract With the increasing market share of Mac OS X over 91% detection accuracy with 3.9% false alarm rate.
  • Webobjects Bundle Reference

    Webobjects Bundle Reference

    WebObjects Bundle Reference 2006-10-03 Times is a registered trademark of Apple Computer, Inc. Heidelberger Druckmaschinen AG, © 2006 Apple Computer, Inc. available from Linotype Library GmbH. All rights reserved. Simultaneously published in the United States and Canada. No part of this publication may be Even though Apple has reviewed this document, reproduced, stored in a retrieval system, or APPLE MAKES NO WARRANTY OR transmitted, in any form or by any means, REPRESENTATION, EITHER EXPRESS OR IMPLIED, WITH RESPECT TO THIS mechanical, electronic, photocopying, DOCUMENT, ITS QUALITY, ACCURACY, recording, or otherwise, without prior MERCHANTABILITY, OR FITNESS FOR A written permission of Apple Computer, Inc., PARTICULAR PURPOSE. AS A RESULT, THIS DOCUMENT IS PROVIDED “AS IS,” AND with the following exceptions: Any person YOU, THE READER, ARE ASSUMING THE is hereby authorized to store documentation ENTIRE RISK AS TO ITS QUALITY AND ACCURACY. on a single computer for personal use only IN NO EVENT WILL APPLE BE LIABLE FOR and to print copies of documentation for DIRECT, INDIRECT, SPECIAL, INCIDENTAL, personal use provided that the OR CONSEQUENTIAL DAMAGES documentation contains Apple’s copyright RESULTING FROM ANY DEFECT OR INACCURACY IN THIS DOCUMENT, even if notice. advised of the possibility of such damages. The Apple logo is a trademark of Apple THE WARRANTY AND REMEDIES SET FORTH ABOVE ARE EXCLUSIVE AND IN Computer, Inc. LIEU OF ALL OTHERS, ORAL OR WRITTEN, EXPRESS OR IMPLIED. No Apple dealer, agent, Use of the “keyboard” Apple logo or employee is authorized to make any (Option-Shift-K) for commercial purposes modification, extension, or addition to this without the prior written consent of Apple warranty.
  • Mac OS X: an Introduction for Support Providers

    Mac OS X: an Introduction for Support Providers

    Mac OS X: An Introduction for Support Providers Course Information Purpose of Course Mac OS X is the next-generation Macintosh operating system, utilizing a highly robust UNIX core with a brand new simplified user experience. It is the first successful attempt to provide a fully-functional graphical user experience in such an implementation without requiring the user to know or understand UNIX. This course is designed to provide a theoretical foundation for support providers seeking to provide user support for Mac OS X. It assumes the student has performed this role for Mac OS 9, and seeks to ground the student in Mac OS X using Mac OS 9 terms and concepts. Author: Robert Dorsett, manager, AppleCare Product Training & Readiness. Module Length: 2 hours Audience: Phone support, Apple Solutions Experts, Service Providers. Prerequisites: Experience supporting Mac OS 9 Course map: Operating Systems 101 Mac OS 9 and Cooperative Multitasking Mac OS X: Pre-emptive Multitasking and Protected Memory. Mac OS X: Symmetric Multiprocessing Components of Mac OS X The Layered Approach Darwin Core Services Graphics Services Application Environments Aqua Useful Mac OS X Jargon Bundles Frameworks Umbrella Frameworks Mac OS X Installation Initialization Options Installation Options Version 1.0 Copyright © 2001 by Apple Computer, Inc. All Rights Reserved. 1 Startup Keys Mac OS X Setup Assistant Mac OS 9 and Classic Standard Directory Names Quick Answers: Where do my __________ go? More Directory Names A Word on Paths Security UNIX and security Multiple user implementation Root Old Stuff in New Terms INITs in Mac OS X Fonts FKEYs Printing from Mac OS X Disk First Aid and Drive Setup Startup Items Mac OS 9 Control Panels and Functionality mapped to Mac OS X New Stuff to Check Out Review Questions Review Answers Further Reading Change history: 3/19/01: Removed comment about UFS volumes not being selectable by Startup Disk.
  • Video Capture 3-In-1 Video Capture

    Video Capture 3-In-1 Video Capture

    Model: NV100C Video Capture 3-in-1 video capture Quick Start Guide 1 Table of Contents Overview ........................................................................................... 3 Package Contents ................................................................................................. 3 System Requirements ........................................................................................... 3 Use on Mac OS .................................................................................. 4 Hardware Installation ........................................................................................... 4 Driver Installation ................................................................................................. 4 Capture Video on QuickTime Player ..................................................................... 4 Use on Windows PC/Laptop ............................................................... 7 Hardware Installation ........................................................................................... 7 Driver Installation ................................................................................................. 7 Capture Video on CyberLink PowerDirector ......................................................... 7 Capture Video on VivaStation............................................................................. 10 Use on Android Device .................................................................... 12 Capture Video on VivaCAP ................................................................................
  • HP Openvms Utility Routines Manual

    HP Openvms Utility Routines Manual

    HP OpenVMS Utility Routines Manual Order Number: BA554-90019 June 2010 This manual describes the OpenVMS utility routines, a set of routines that provide a programming interface to various OpenVMS utilities. Revision/Update Information: This manual supersedes the HP OpenVMS Utility Routines Manual, OpenVMS Alpha Version 8.3. Software Version: OpenVMS Version 8.4 for Integrity servers OpenVMS Alpha Version 8.4 Hewlett-Packard Company Palo Alto, California © Copyright 2010 Hewlett-Packard Development Company, L.P. Confidential computer software. Valid license from HP required for possession, use or copying. Consistent with FAR 12.211 and 12.212, Commercial Computer Software, Computer Software Documentation, and Technical Data for Commercial Items are licensed to the U.S. Government under vendor’s standard commercial license. The information contained herein is subject to change without notice. The only warranties for HP products and services are set forth in the express warranty statements accompanying such products and services. Nothing herein should be construed as constituting an additional warranty. HP shall not be liable for technical or editorial errors or omissions contained herein. Intel and Itanium are trademarks or registered trademarks of Intel Corporation or its subsidiaries in the United States and other countries. ZK4493 The HP OpenVMS documentation set is available on CD. This document was prepared using DECdocument, Version 3.3-1B. Contents Preface ............................................................ xvii 1 Introduction to Utility Routines 2 Access Control List (ACL) Editor Routine 2.1 Introduction to the ACL Editor Routine ........................... ACL–1 2.2 Using the ACL Editor Routine: An Example ....................... ACL–1 2.3 ACL Editor Routine . ........................................ ACL–2 ACLEDIT$EDIT ...........................................
  • OS X Mavericks

    OS X Mavericks

    OS X Mavericks Core Technologies Overview October 2013 Core Technologies Overview 2 OS X Mavericks Contents Page 4 Introduction Page 5 System Startup BootROM EFI Kernel Drivers Initialization Address Space Layout Randomization (ASLR) Compressed Memory Power Efficiency App Nap Timer Coalescing Page 10 Disk Layout Partition Scheme Core Storage File Systems Page 12 Process Control Launchd Loginwindow Grand Central Dispatch Sandboxing GateKeeper XPC Page 19 Network Access Ethernet Wi-Fi Multihoming IPv6 IP over Thunderbolt Network File Systems Access Control Lists Directory Services Remote Access Bonjour Page 25 Document Lifecycle Auto Save Automatic Versions Document Management Version Management iCloud Storage Core Technologies Overview 3 OS X Mavericks Page 28 Data Management Spotlight Time Machine Page 30 Developer Tools Xcode LLVM Instruments Accelerate Automation WebKit Page 36 For More Information Core Technologies Overview 4 OS X Mavericks Introduction With more than 72 million users—consumers, scientists, animators, developers, and system administrators—OS X is the most widely used UNIX® desktop operating system. In addition, OS X is the only UNIX environment that natively runs Microsoft Office, Adobe Photoshop, and thousands of other consumer applications—all side by side with traditional command-line UNIX applications. Tight integration with hardware— from the sleek MacBook Air to the powerful Mac Pro—makes OS X the platform of choice for an emerging generation of power users. This document explores the powerful industry standards and breakthrough innovations in the core technologies that power Apple’s industry-leading user experiences. We walk you through the entire software stack, from firmware and kernel to iCloud and devel- oper tools, to help you understand the many things OS X does for you every time you use your Mac.
  • The 6 Key Benefits of Being an Api-Centric Organization

    The 6 Key Benefits of Being an Api-Centric Organization

    THE 6 KEY BENEFITS OF BEING AN API-CENTRIC ORGANIZATION © 2019 Radical I/O Technology Inc. FOREWORD Digital transformation is about more than adopting the latest technologies. It is about maximizing value by using technology to improve efficiency and productivity, drive engagement and growth, and ultimately make the lives of customers, partners and staff better. APIs play an integral role as the connectors between the systems, data, and people that enable digital transformation initiatives. This guide, the first in our series exploring API best practices, therefore focuses on what APIs are, how they work, and outlines six benefits they offer for achieving organizational goals. Radical I/O is a people-first technology consultancy and lab in Vancouver, BC that specializes in data-driven enterprise software development with highly performant API architecture at its core. We understand that the needs of private and public organizations are continually evolving, and we enjoy working collaboratively with our clients and partners to create forward-thinking technology solutions. IAN SIM Chief Technology Officer Radical I/O Technology [email protected] © 2019 Radical I/O Technology Inc. THE 6 KEY BENEFITS OF BEING AN API-CENTRIC ORGANIZATION 3 CONTENTS There’s an API for that ..........................................................................1 What is an API? ..................................................................................... 2 Types of APIs ...........................................................................................4
  • VSI OMNI API for Openvms Installation Guide

    VSI OMNI API for Openvms Installation Guide

    VSI OMNI API for OpenVMS Installation Guide Document Number: DO-DOMNI2-01A Publication Date: April 2018 This manual describes the prerequisites and procedures for installing the VSI OMNI Application Programming Interface (API) software on VSI OpenVMS platforms. Operating System: VSI OpenVMS Integrity Version 8.4-1H1 VSI OpenVMS Alpha Version 8.4-2L1 Software Version: VSI OMNI Version 4.1 VMS Software, Inc., (VSI) Bolton, Massachusetts, USA VSI OMNI API for OpenVMS Installation Guide Copyright © 2018 VMS Software, Inc., (VSI), Bolton Massachusetts, USA Legal Notice Confidential computer software. Valid license from VSI required for possession, use or copying. Consistent with FAR 12.211 and 12.212, Commercial Computer Software, Computer Software Documentation, and Technical Data for Commercial Items are licensed to the U.S. Government under vendor's standard commercial license. The information contained herein is subject to change without notice. The only warranties for VSI products and services are set forth in the express warranty statements accompanying such products and services. Nothing herein should be construed as constituting an additional warranty. VSI shall not be liable for technical or editorial errors or omissions contained herein. HPE, HPE Integrity, HPE Alpha, and HPE Proliant are trademarks or registered trademarks of Hewlett Packard Enterprise. Intel, Itanium and IA64 are trademarks or registered trademarks of Intel Corporation or its subsidiaries in the United States and other countries. Microsoft, Windows, Windows-NT and Microsoft XP are U.S. registered trademarks of Microsoft Corporation. Microsoft Vista is either a registered trademark or trademark of Microsoft Corporation in the United States and/or other countries.