DOCSLIB.ORG

Introduc^On to Oauth

Total Page：16

File Type：pdf, Size：1020Kb

Download full-text PDF Read full-text
Introduc^On to Oauth Introduc)on to OAuth 2.0 Jus)n Richer ©2016 Bespoke Engineering LLC Bespoke Engineering 1 APIs are meant to be used • Much of my data and the func)onality of my life is available through APIs today • I want to have applicaons access my APIs • I don’t want the applicaons to have to impersonate me ©2016 Bespoke Engineering LLC • I don’t want to share my keys with everyone 2 A valet key for APIs • A valet key gives someone else limited access to a car • What if we could do that for web APIs? ©2016 Bespoke Engineering LLC 3 OAUTH 2.0 ©2016 Bespoke Engineering LLC 4 From the spec (RFC6749) The OAuth 2.0 authorization framework enables a third-party application to obtain limited access to an HTTP service, either on behalf of a resource owner by orchestrating an approval interaction between the resource owner and the HTTP service, or by allowing the third-party application to obtain access on its ©2016 Bespoke Engineering LLC own behalf. 5 The good bits The OAuth 2.0 authorization framework enables a third-party application to obtain limited access to an HTTP service, either on behalf of a resource owner by orchestrating an approval interaction between the resource owner and the HTTP service, or by allowing the third-party application to obtain access on its ©2016 Bespoke Engineering LLC own behalf. 6 In other words OAuth 2.0 is a delegation protocol that lets people allow applications to access things (like APIs) on their behalf. ©2016 Bespoke Engineering LLC 7 Who is involved? Resource Authorization Owner Server ©2016 Bespoke Engineering LLC Client Protected Resource 8 The resource owner • Has access to some resource or API • Can delegate access to that resource or API • Usually has access to a web browser • Usually is a person ©2016 Bespoke Engineering LLC 9 The protected resource • Web service (API) with security controls • Protects things for the resource owner • Shares things on the resource owner’s request ©2016 Bespoke Engineering LLC 10 The client applicaon • Wants to access the protected resource • Does things on the resource owner’s behalf • Could be a web server – But it’s s)ll a “client” in OAuth parlance – Could also be a nave app or JS app ©2016 Bespoke Engineering LLC 11 What are we trying to solve? The Goal: Resource Owner Give the client access to the protected resource on behalf of the resource owner. ©2016 Bespoke Engineering LLC Client Protected Resource 12 Introducing the Authorizaon Server (AS) The Authorization Server gives us a mechanism to Resource Authorization Owner bridge the gap between Server the client and the protected resource ©2016 Bespoke Engineering LLC Client Protected Resource 13 The Authorizaon Server • Generates tokens for the client • Authen)cates resource owners (users) • Authen)cates clients • Manages authorizaons ©2016 Bespoke Engineering LLC 14 OAuth Tokens • Represent granted delegated authori)es – From the resource owner to the client for the protected resource • Issued by authorizaon server • Used by client – Format is opaque to clients ©2016 Bespoke Engineering LLC • Consumed by protected resource 15 Example OAuth Tokens • 92d42038006dba95d0c501951ac5b5eb • 2df029c6-b38d-4083-b8d9-db67c774d13f • eyJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCJ9.eyJzdWIiO iIxMjM0NTY3ODkwIiwibmFtZSI6IkpvaG4gRG9lIiw iYWRtaW4iOnRydWV9.TJVA95OrM7E2cBab30RM HrHDcEfxjoYZgeFONFh7HgQ ©2016 Bespoke Engineering LLC • waterbuffalo-elephant-helicopter-argument 16 The OAuth approach at the AS • Client authen)cates for itself • User authorizes client to act on user’s behalf • Server generates a token to represent that authorizaon • Client presents that token to gain access ©2016 Bespoke Engineering LLC 17 You’ve used OAuth ©2016 Bespoke Engineering LLC 18 The pieces of OAuth Resource Authorization Owner Server Access Token ©2016 Bespoke Engineering LLC Client Protected Resource 19 THE AUTHORIZATION CODE FLOW A deep dive into the canonical OAuth 2.0 transac)on ©2016 Bespoke Engineering LLC 20 The authorizaon code flow Resource Authorization Owner Server ©2016 Bespoke Engineering LLC Client Protected Resource 21 TWO FORMS OF COMMUNICATION ©2016 Bespoke Engineering LLC 22 The front channel Resource Front channel uses Authorization Owner HTTP redirects through Server the web browser, no direct connections ©2016 Bespoke Engineering LLC Client Protected Resource 23 The back channel Back channel uses direct HTTP connections between components, the browser is not involved Resource Authorization Owner Server ©2016 Bespoke Engineering LLC Client Protected Resource 24 THE AUTHORIZATION CODE FLOW Step by step ©2016 Bespoke Engineering LLC 25 Authorizaon Code: Step 1 Resource Client redirects the Authorization Owner resource owner to the Server authorization server ©2016 Bespoke Engineering LLC Client Protected Resource 26 Authorizaon Code: Step 2 Resource Resource owner Authorization Owner authenticates to the Server authorization server ©2016 Bespoke Engineering LLC Client Protected Resource 27 Authorizaon Code: Step 3 ? Resource Resource owner Authorization Owner authorizes the client Server ©2016 Bespoke Engineering LLC Client Protected Resource 28 A layered trust model • Centralized control Whitelist • Traditional policy management Internal parties Known business partners Customer organizations Trust frameworks • End user decisions Greylist • Extensive auditing and logging • Rules on when to move to the Unknown entities white or black lists Trust On First Uuse • Centralized control Blacklist • Traditional policy management Known bad parties ©2016 Bespoke Engineering LLC Attack sites 29 Authorizaon Code: Step 4 Resource Authorization server Authorization Owner redirects resource owner Server back to the client with an authorization code ©2016 Bespoke Engineering LLC Client Protected Resource 30 Authorizaon Code: Step 5 Client sends the authorization code back to the authorization server along with its own credentials Resource Authorization Owner Server ©2016 Bespoke Engineering LLC Client Protected Resource 31 Authorizaon Code: Step 6 Authorization server issues OAuth token to the client Resource Authorization Owner Server ©2016 Bespoke Engineering LLC Client Protected Resource 32 Authorizaon Code: Step 7 Resource Client accesses the Authorization Owner protected resource using Server the access token ©2016 Bespoke Engineering LLC Client Protected Resource 33 Interpre)ng the token • The client never knows or cares what’s in the token itself • The resource server needs to understand what’s in the token – Who it’s issued for ©2016 Bespoke Engineering LLC – What it’s good for 34 Thank You ©2016 Bespoke Engineering LLC 35 BACKUP SLIDES Here there be dragons ©2016 Bespoke Engineering LLC 36 OTHER WAYS TO DO OAUTH 2.0 ©2016 Bespoke Engineering LLC 37 The implicit flow Resource Client Inside Authorization Owner the Browser Server Implicit grant type uses only the front channel since the client is inside the browser ©2016 Bespoke Engineering LLC Protected Resource 38 The client creden)als flow Client credentials grant type: Client trades its own credentials for a token, uses only the back channel since the client is acting on its own behalf Authorization Server ©2016 Bespoke Engineering LLC Client Protected Resource 39 The resource owner password flow Resource owner credentials grant type: Client trades username and password for an OAuth token over the back channel Resource Authorization Owner Server ? ©2016 Bespoke Engineering LLC Client Protected Resource 40 The asser)ons flows Client trades a cryptographically protected element (assertion) for a token Assertion provider Authorization Server ©2016 Bespoke Engineering LLC Client Protected Resource 41 Different use cases • Authorizaon code flow: web applicaons, some nave applicaons • Implicit flow: in-browser applicaons • Client creden)als flow: non-interac)ve • Password flow: trusted legacy clients ©2016 Bespoke Engineering LLC • Asser)on flows: trust frameworks 42 How to choose a flow Is the client acting on Can the resource owner Is the client running Yes Yes Yes behalf of a resource interact with a web browser completely inside of a owner? while using the client? web browser? Implicit No No Does the user have a simple set of credentials No like a password? Authorization Yes Code Resource Owner Credentials Choose the appropriate Is the client acting Client on its own behalf? Yes Credentials OAuth grant type for No the type of application Is the client acting on Yes you’re building ©2016 Bespoke Engineering LLC behalf of a third party authority? Assertion 43 CAN WE BUILD AUTHENTICATION ON OAUTH? ©2016 Bespoke Engineering LLC 44 How can we split the network? Security Domain Boundary Security Resource Client Protected Authorization Owner Resource Server OAuth Sign-In The security domain boundary is crossed User Relying Party ©2016 Bespoke Engineering LLC Identity Provider 45 A bemer way to split the network Security Domain Boundary Security + Resource Client Protected Authorization Owner Resource Server OAuth Sign-In The security domain boundary is preserved User Relying Party ©2016 Bespoke Engineering LLC Identity Provider 46 That works! • We’re using OAuth to protect the iden)ty • The client consumes the iden)ty ©2016 Bespoke Engineering LLC 47 Authorizaon is Chocolate • Good on its own • Great as part of a larger recipe • Many different recipes can use it ©2016 Bespoke Engineering LLC 48 Authen)caon is Fudge • Confec)on with several ingredients • Tends to have one flavor as the most obvious • Could be made using chocolate – But not required ©2016 Bespoke Engineering LLC 49 Agreeing on a recipe • Let’s
Load more

Recommended publications
  • Raw Slides (Pdf)
    2550 Intro to cybersecurity L5: Distributed Authentication abhi shelat/Ran Cohen Agenda • The problem of distributed authentication • The Needham-Schroeder protocol • Kerberos protocol • Oauth So far: authenticating to a server Mallory Alice Bob Gen pw pw Authenticating to an organization Mallory Alice Gen pw pw Authenticating to an organization Mallory Alice Gen pw pw Distributed authentication • Organizations have many entities (users/services) • Secure communication over insecure channels • Password-based authentication • Passwords are never transmitted (except for the setup phase) • Enable mutual authentication Basic tool: symmetric encryption Alice Bob 푚 푚 Eve Basic tool: symmetric encryption • Gen: generates secret key 푘 • Enc: given 푘 and 푚 output a ciphertext 푐 Denote 퐸푛푐푘 푚 , 퐸푘 푚 , 푚 푘 • Dec: given 푘 and 푐 output a message 푚 • Security (informal): Whatever Eve can learn on 푚 given 푐 can be learned without 푐 • Examples: – DES (Data Encryption Standard) – AES (Advanced Encryption Standard) 푚 Authentication from Encryption • Alice and Bob share a key • They communicate over an insecure channel • Alice wants to prove her identity to Bob • Eve’s goal: impersonate Alice Alice Bob 푘퐴퐵 푘퐴퐵 Eve Attempt #1 Alice Bob I am Alice 푘퐴퐵 푘퐴퐵 I am Alice Eve Attempt #2: use the key Alice Bob I am Alice 푘퐴퐵 푘퐴퐵 푘퐴퐵 I am Alice 푘퐴퐵 Replay attack Eve Attempt #3: use nonce Alice I am Alice Bob 푁푎 푘퐴퐵 Pay Eve 500$ 푁푎 − 1 푘퐴퐵 푘퐴퐵 푘퐴퐵 푘퐴퐵 Nonce: a random number for a one-time use Eve Attempt #3: use nonce Alice I am Alice Bob 푁푎 푘퐴퐵 Pay Eve 500$ 푁푎 −
    [Show full text]
  • The Essential Oauth Primer: Understanding Oauth for Securing Cloud Apis
    THE ESSENTIAL OAUTH PRIMER: UNDERSTANDING OAUTH FOR SECURING CLOUD APIS WHITE PAPER TABLE OF CONTENTS 03 EXECUTIVE OVERVIEW 03 MOTIVATING USE CASE: TRIPIT 05 TERMINOLOGY 06 INTRODUCTION 07 THE OAUTH 2.0 MODEL 07 OAUTH 2.0 OVERVIEW USING A TOKEN TOKEN TYPE 09 RELATIONSHIP TO OTHER STANDARDS 11 USE CASES TRIPIT REVISITED TOKEN EXCHANGE MOBILE WORKFORCE 13 RECENT DEVELOPMENT 14 SUMMARY 2 WHITE PAPER ESSENTIAL OAUTH PRIMER EXECUTIVE OVERVIEW A key technical underpinning of the cloud and the Internet of Things are Application Programming Interfaces (APIs). APIs provide consistent methods for outside entities such as web services, clients and desktop applications to interface with services in the cloud. More and more, cloud data will move through APIs, but the security and scalability of APIs are currently threatened by a problem call the password anti-pattern. This is the need for API clients to collect and replay the password for a user at an API in order to access information on behalf of that user via that API. OAuth 2.0 defeats the password anti-pattern, creating a consistent, flexible identity and policy architecture for web applications, web services, devices and desktop clients attempting to communicate with cloud APIs. MOTIVATING USE CASE: TRIPIT Like many applications today, TripIt (http://tripit.com) is a cloud-based service. It’s a travel planning application that allows its users to track things like flights, car rentals, and hotel stays. Users email their travel itineraries to TripIt, which then builds a coordinated view of the users’ upcoming trips (as well as those of their TripIt friends—the inevitable social aspect).
    [Show full text]
  • OK: Oauth 2.0 Interface for the Kerberos V5 Authentication Protocol
    OK: OAuth 2.0 interface for the Kerberos V5 Authentication Protocol James Max Kanter Bennett Cyphers Bruno Faviero John Peebles [email protected] [email protected] [email protected] [email protected] 1. Problem Kerberos is a powerful, convenient framework for user authentication and authorization. Within MIT, Kerberos is used with many online institute services to verify users as part of Project Athena. However, it can be difficult for developers unfamiliar with Kerberos development to take advantage of its resources for use in third-party apps. OAuth 2.0 is an open source protocol used across the web for secure delegated access to resources on a server. Designed to be developer-friendly, OAuth is the de facto standard for authenticating users across sites, and is used by services including Google, Facebook, and Twitter. Our goal with OK Server is to provide an easy way for developers to access third-party services using Kerberos via OAuth. The benefits of this are twofold: developers can rely on an external service for user identification and verification, and users only have to trust a single centralized server with their credentials. Additionally, developers can request access to a subset of Kerberos services on behalf of a user. 2. Implementation overview Our system is composed of two main components: a server (the Kerberos client) to retrieve and process tickets from the MIT KDC, and an OAuth interface (the OAuth server) to interact with a client app (the app) wishing to make use of Kerberos authentication. When using our system, a client application uses the OAuth protocol to get Kerberos service tickets for a particular user.
    [Show full text]
  • Vmware Workspace ONE Access 20.01 Managing User Authentication Methods in Vmware Workspace ONE Access
    Managing User Authentication Methods in VMware Workspace ONE Access JAN 2020 VMware Workspace ONE Access 20.01 Managing User Authentication Methods in VMware Workspace ONE Access You can find the most up-to-date technical documentation on the VMware website at: https://docs.vmware.com/ VMware, Inc. 3401 Hillview Ave. Palo Alto, CA 94304 www.vmware.com © Copyright 2020 VMware, Inc. All rights reserved. Copyright and trademark information. VMware, Inc. 2 Contents 1 Configuring Authentication in VMware Workspace ONE Access 5 2 User Auth Service Authentication Methods in Workspace ONE Access 8 Configuring Password (Cloud) Authentication in Workspace ONE Access 9 Configure Password (Cloud) Authentication with Your Enterprise Directory 10 Configuring RSA SecurID (Cloud) For Workspace ONE Access 13 Prepare the RSA SecurID Server 13 Configure RSA SecurID Authentication in Workspace ONE Access 14 Configuring RADIUS for Workspace ONE Access 16 Prepare the RADIUS Server 16 Configure RADIUS Authentication in Workspace ONE Access 16 Enable User Auth Service Debug Logs In Workspace ONE Access Connector 19 3 Configuring Kerberos Authentication In Workspace ONE Access 21 Configure and Enable Kerberos Authentication in Workspace ONE Access 21 Configuring your Browser for Kerberos 23 Configure Internet Explorer to Access the Web Interface 23 Configure Firefox to Access the Web Interface 24 Configure the Chrome Browser to Access the Web Interface 25 Kerberos Initialization Error in Workspace ONE Access 26 4 Associate Workspace ONE Access Authentication Methods
    [Show full text]
  • Nist Sp 800-77 Rev. 1 Guide to Ipsec Vpns
    NIST Special Publication 800-77 Revision 1 Guide to IPsec VPNs Elaine Barker Quynh Dang Sheila Frankel Karen Scarfone Paul Wouters This publication is available free of charge from: https://doi.org/10.6028/NIST.SP.800-77r1 C O M P U T E R S E C U R I T Y NIST Special Publication 800-77 Revision 1 Guide to IPsec VPNs Elaine Barker Quynh Dang Sheila Frankel* Computer Security Division Information Technology Laboratory Karen Scarfone Scarfone Cybersecurity Clifton, VA Paul Wouters Red Hat Toronto, ON, Canada *Former employee; all work for this publication was done while at NIST This publication is available free of charge from: https://doi.org/10.6028/NIST.SP.800-77r1 June 2020 U.S. Department of Commerce Wilbur L. Ross, Jr., Secretary National Institute of Standards and Technology Walter Copan, NIST Director and Under Secretary of Commerce for Standards and Technology Authority This publication has been developed by NIST in accordance with its statutory responsibilities under the Federal Information Security Modernization Act (FISMA) of 2014, 44 U.S.C. § 3551 et seq., Public Law (P.L.) 113-283. NIST is responsible for developing information security standards and guidelines, including minimum requirements for federal information systems, but such standards and guidelines shall not apply to national security systems without the express approval of appropriate federal officials exercising policy authority over such systems. This guideline is consistent with the requirements of the Office of Management and Budget (OMB) Circular A-130. Nothing in this publication should be taken to contradict the standards and guidelines made mandatory and binding on federal agencies by the Secretary of Commerce under statutory authority.
    [Show full text]
  • Cloudvision As-A-Service (Cvaas) Quick Start Guide
    CloudVision as-a-Service (CVaaS) Quick Start Guide Arista Networks www.arista.com September 2021 Headquarters Support Sales 5453 Great America Parkway +1 408 547-5502 +1 408 547-5501 Santa Clara, CA 95054 +1 866 476-0000 +1 866 497-0000 USA [email protected] [email protected] +1 408 547-5500 www.arista.com © Copyright 2021 Arista Networks, Inc. All rights reserved. The information contained herein is subject to change without notice. The trademarks, logos and service marks ("Marks") displayed in this documentation are the property of Arista Networks in the United States and other countries. Use of the Marks are subject to Arista Network’s Term of Use Policy, available at www.arista.com/en/terms-of-use. Use of marks belonging to other parties is for informational purposes only. ii Contents Contents 1 CloudVision as-a-Service....................................................................1 1.1 Onboarding at a Glance.........................................................................................................1 1.2 User Onboarding Prerequisites.............................................................................................. 3 1.2.1 Invitation URL........................................................................................................... 3 1.2.2 Authentication Details............................................................................................... 3 1.3 User Onboarding Workflow.................................................................................................... 4 1.3.1
    [Show full text]
  • Single Sign-On the Way It Should Be
    Single sign-on the way it should be 6 ways Citrix Workspace delivers seamless access to all apps while improving security and the user experience Contents Single sign-on (SSO) solutions .......................................................................3 Secure access to everything ...........................................................................5 Granular controls for SaaS apps and the web ...........................................6 Control over your user identity ......................................................................7 Security beyond user names and passwords ............................................8 Seamless integration with your existing environment ..........................9 Resolving issues faster with end-to-end visibility ............................... 10 ↑ Back← Pg. to 2 contents | Pg. 4 → Citrix.com 2 Single sign-on (SSO) solutions were designed to make life easier for employees and IT. They’re meant to reduce the cost of management and provide better security, all while delivering an improved user experience. However, many solutions fall short, covering only one type or a subset of application types. This forces you to implement several access solutions from different vendors to cover your entire application landscape — negating the productivity and user experience benefits you hoped for. The complexity this type of implementation creates also runs counter to the Zero Trust initiatives that many organizations are undertaking Citrix Workspace helps you unify all apps and data across your distributed IT architecture to provide single sign-on to all the applications and data people need to be productive. Working with your existing infrastructure, Citrix Access Control consolidates multiple remote access solutions, like traditional VPNs or SSO solutions, simplifying management for IT and providing unified access for employees. ↑ Back to contents ← Pg. 2 | Pg. 4 → 3 Citrix.com | e-book | Choosing a Single Sign-On Solution ↓ 6 benefits of the Citrix Workspace SSO solution ↑ ← Pg.
    [Show full text]
  • Securing Digital Identities in the Cloud by Selecting an Apposite Federated Identity Management from SAML, Oauth and Openid Connect
    Securing Digital Identities in the Cloud by Selecting an Apposite Federated Identity Management from SAML, OAuth and OpenID Connect Nitin Naik and Paul Jenkins Defence School of Communications and Information Systems Ministry of Defence, United Kingdom Email: [email protected] and [email protected] Abstract—Access to computer systems and the information this sensitive data over insecure channels poses a significant held on them, be it commercially or personally sensitive, is security and privacy risk. This risk can be mitigated by using naturally, strictly controlled by both legal and technical security the Federated Identity Management (FIdM) standard adopted measures. One such method is digital identity, which is used to authenticate and authorize users to provide access to IT in the cloud environment. Federated identity links and employs infrastructure to perform official, financial or sensitive operations users’ digital identities across several identity management within organisations. However, transmitting and sharing this systems [1], [2]. FIdM defines a unified set of policies and sensitive information with other organisations over insecure procedures allowing identity management information to be channels always poses a significant security and privacy risk. An transportable from one security domain to another [3], [4]. example of an effective solution to this problem is the Federated Identity Management (FIdM) standard adopted in the cloud Thus, a user accessing data/resources on one secure system environment. The FIdM standard is used to authenticate and could then access data/resources from another secure system authorize users across multiple organisations to obtain access without both systems needing individual identities for the to their networks and resources without transmitting sensitive single user.
    [Show full text]
  • Recent Evolutions in the Oauth 2.0 and Openid Connect Landscape
    RECENT EVOLUTIONS IN THE OAUTH 2.0 AND OPENID CONNECT LANDSCAPE DR. PHILIPPE DE RYCK https://Pragmatic Web Security.com DR. PHILIPPE DE RYCK - Deep understanding of the web security landscape - Google Developer Expert (not employed by Google) - Course curator of the SecAppDev course (https://secappdev.org) Pragmatic Web Security High-quality security training for developers and managers Custom courses covering web security, API security, Angular security, … Consulting services on security, Oauth 2.0, OpenID Connect, … @PHILIPPEDERYCK @PhilippeDeRyck HTTPS://PRAGMATICWEBSECURITY.COM2 User authentication Read & write data @PhilippeDeRyck 3 User authentication Read & write data @PhilippeDeRyck 4 User authentication Read & write data @PhilippeDeRyck 5 OpenID Connect User authentication Read & write data OAuth 2.0 @PhilippeDeRyck 6 OpenID Connect User authentication Read & write data Read data OAuth 2.0 OAuth 2.0 @PhilippeDeRyck 7 Results in an identity token and access token User authentication Read & write data Read data Uses an access Uses an access token token @PhilippeDeRyck 8 OAUTH 2.0 AND OPENID CONNECT OpenID Connect provides user authentication OAuth 2.0 allows a client to access resources on behalf of the user Modern applications use a combination of both protocols @PhilippeDeRyck 9 THE OIDC HYBRID FLOW 5 Request client authorization 3 Authenticate yourself 4 Login credentials 6 Authorize client Authorization code 10 11 Access token / refresh token Redirect for with client credentials authentication 2 Redirect with 7 authorization
    [Show full text]
  • Fortiauthenticator Administration Guide Contains the Following Sections
    FortiAuthenticator - Administration Guide Version 6.2.0 FORTINET DOCUMENT LIBRARY https://docs.fortinet.com FORTINET VIDEO GUIDE https://video.fortinet.com FORTINET BLOG https://blog.fortinet.com CUSTOMER SERVICE & SUPPORT https://support.fortinet.com FORTINET TRAINING & CERTIFICATION PROGRAM https://www.fortinet.com/support-and-training/training.html NSE INSTITUTE https://training.fortinet.com FORTIGUARD CENTER https://fortiguard.com/ END USER LICENSE AGREEMENT https://www.fortinet.com/doc/legal/EULA.pdf FEEDBACK Email: [email protected] January 15, 2021 FortiAuthenticator 6.2.0 Administration Guide 23-620-657445-20210115 TABLE OF CONTENTS Change Log 9 What's new in FortiAuthenticator 10 FortiAuthenticator 6.2.0 10 REST API enhancements 10 TACACS+ support 10 SAML IdP Proxy: 0365 Azure/ADFS hybrid support 10 Get Windows AD nested groups during SAML IdP configuration 10 REST API key visibility for Admin users 11 RADSEC support 11 SCEP enrollment requests search 11 LDAP group filter support for remote RADIUS realms 11 Sync certificate bindings to load balancers 11 Show Password toggle included in replacement messages 11 Legacy Self-service Portal disabled by default 12 Additional SCEP CRL/OCSP enrollment options 12 Revoked/expired user certificates hidden by default 12 Richer logs for self-registered users 12 Usernames included in FTM activation messages 12 FTC: Sync email and mobile number 13 SNMP trap for RAID status changes 13 Administrator password required before changes can be made to administrator accounts 13 FortiAuthenticator
    [Show full text]
  • CAS Sessions Might Run Under the CAS Instance's Service Account Or the End User's Identity
    Paper SAS4613-2020 SAS® Cloud Analytic Services Sessions: Understanding Connection Options to Ensure Data Access Security Philip Hopkins, SAS Institute Inc. ABSTRACT In SAS® Viya®, there are a variety of ways to connect to the SAS® Cloud Analytic Services (CAS) analytics engine, or CAS server. The resulting CAS sessions might run under the CAS instance's service account or the end user's identity. This is further complicated by whether the CAS client is using the Kerberos authentication protocol, which results in differences, depending on whether CAS is running on Linux or Windows. The various SAS Viya applications default to certain connection methods, which drive their CAS session's process owner and, finally, the resulting physical security contexts. Understanding the default CAS session behavior for each application and how those defaults can be overridden and engineered to support data access policy is the focus of this paper. INTRODUCTION SAS Viya includes multiple run-time engines that offer the ability to do valuable compute processing. The traditional SAS® Programming Runtime Environment (SPRE) lives on in SAS Viya1 alongside the SAS Cloud Analytic Services (CAS) in-memory analytics engine and the SAS® Micro Analytic Service (MAS). When these runtime engines access sensitive data sources, their sessions should be instantiated in a manner that will ensure data access in compliance with your security policies. CAS is the primary engine for performing analytics and batch scoring on large in-memory tables at the speed of random-access memory (RAM). CAS sessions are capable of accessing external data sources from a variety of data providers and loading that data into memory creating CAS tables for analysis.
    [Show full text]
  • Data Source Kerberos / Oauth on the Wire Explaining Kerberos Constrained Delegation with Protocol Transition and Oauth for Data Source Single Sign On
    Welcome 1 8 B I - 11 3 Data Source Kerberos / oAuth On the Wire Explaining Kerberos Constrained Delegation with Protocol Transition and Oauth for Data Source Single Sign On John Kew Speaker Name (if needed) Manager / Connectivity Job Title Tableau Company / Org Name Explaining Kerberos Constrained Delegation with Protocol Transition And oAuth for Data Source Single Sign On Everyone dreams of SSO via anything but Kerberos Agenda Server settings SQL Server impersonation User filters and data source filters Run as user oAuth connections Enable Kerberos delegation User Filters and Data Source Filters Run as User Oauth (and SAML) Why Kerberos? Two-Factor Auth Trust Constrained Delegation Introducing Bagel DB Bageld—Bagel Database of the Future /* Bageld - A system for the organization, storage, and retrieval of Bagel information John V. Kew Assignment 2 CPEx317 w/ Dr. Nico Winter, 2002 This program sets up a decision tree for the organization of bagel information. The program will use a database file in the local directory called "bagels.db" - If this file does not exist, it will create it so that bagel information can be added. Files: bageld.c bageld.h string.c string.h Compilation: Use cmake Usage: ./bageld [bagel database] [optional: kerberos keytab] Without a database, the program will first ask you for a bagel type. Then begin filling the database with Caleb bagels, Monkey bagels, and Toast bagels. All answers are of "yes", "no", [Bagel Name], or a question about a bagel. */ Bageld—Bagel Database of the Future Bagels + Kerberos = Enterprise Single Hop Kerberos with Bagel DB Casting Call Narrator: John Kew Alice the Bagel Database: Jason Burns Microsoft Bob the Active Directory Server: <INSERT YOU> Eve the Bagel Database Client: <INSERT YOU> Single Hop Kerberos: The Setup Narrator: A bagel shop.
    [Show full text]