DOCSLIB.ORG

Cloud Foundry: Deploying to the Cloud

Total Page：16

File Type：pdf, Size：1020Kb

Download full-text PDF Read full-text
Cloud Foundry: Deploying to the Cloud APPENDIXA Cloud Foundry: Deploying to the Cloud In this appendix, we will discuss what it takes to get our application to run on a different environment than what we have been running it on so far. Instead of running on any boring old Tomcat instance, we'll run it in the cloud. But before we get down to it, we'll talk just a little bit about what the cloud means. Cloud Computing You probably haven't been able to avoid the onslaught of cloud computing in the specialized media. But you may still not have an idea of what cloud computing entails. We'll try to give a short overview of what cloud computing is about. It's hard to give a single definition of what cloud computing is, as it tends to mean different things to different people. One broader definition goes like this: Cloud Computing is a distributed computing model consisting of three ti ers­ infrastructure, platform, and serv ices-that enables ubiquitous, convenient, on­ demand network access to ash ared pool of configurable computing resources (e.g., networks, servers, storage, applications, and services). Consider Amazon S3,1 for example: Amazon allows you to store data on its servers using web-based APIs. You pay Amazon for the bandwidth you use in uploading or downloading that data. At no point in time do you ever need to have your own storage infrastructure. There are several kinds of cloud service models in use: • Infrastructure as a service (laaS): Delivers computing infrastructure as a service. Examples of such infrastructure include virtual computers, storage, network infrastructure, and so forth. This is more the realm of sysadmins than developers. Amazon and Rackspace are two of the best-known IaaS providers. lhttp://aws.amazon.com/es/s3/ 535 APPENDIX A • CLOUD FOUNDRY: DEPLOYING TO THE CLOUD • Platform as a service (PaaS): Offers services beyond the infrastructure. Here, the emphasis is on the development environment, application services, and application-deployment mechanisms. The control over the actual infrastructure itself is mostly handed by the service provider. Good examples of a PaaS approach are Google App Engine and Cloud Foundry. • Software as a service (SaaS): Provides the delivery of a full solution as a service, eliminating the need to install and run the application on the customer's own computers and simplifying maintenance and support. Contrast this with the traditional delivery model for software, where end users install software on every desktop, manage the upgrades themselves, and so on. In this model, the user just visits a website and begins using the application online. Google Docs is a good example of a SaaS. Cloud Foundry In this appendix, we'll use Cloud Foundry as our PaaS of choice to deploy our bookstore application to. But what is Cloud Foundry and why would we want to use it? Cloud Foundry describes itself like this: [Cloud Foundry is] an open platform as a service, providing a cho ice of clouds, developer frameworks and application services. Initiated by VMware, with broad industry support, Cloud Foundry makes itfaster and easier to build, test, deploy and scale applications. It is an open source project and is available through a variety 0 f private cloud distributions and public cloud i nstances, including CloudFoundry.com. 2 Now what does this mean? It means that Cloud Foundry is not a proprietary, vendor-specific PaaS, but a truly open platform that is being developed by several individuals and organizations. For example, ActiveState offers Stackato,3 an expansion of Cloud Foundry that offers Python, PHP, and Perl support. Ubuntu is also working on supporting Cloud Foundry under their Ubuntu Cloud4banner. It also means that we have to define some things more explicitly: • Cloud Foundry is the name of the open source project. You can fmd the code for this on github;5 its website is at www. cloudfoundry. org. • Cloudfoundry.com is a VMWare-hosted instance of Cloud Foundry that lets you deploy your application on VMWare-owned infrastructure. In the course of this appendix, we don't differentiate between Cloud Foundry the platform and CloudFoundry.com the hosted service. 2http://www.cloudfoundry.com 3http://www.activestate.com/stackato 4http://cloud.ubuntu.com 5https:llgithub.com/cloudfoundry/ 536 APPENDIX A • CLOUD FOUNDRY: DEPLOYING TO THE CLOUD Now that we've seen what Cloud Foundry is, why should we as Java/Spring developers care? Why should we use it over any other PaaS? One reason: The fact that Cloud Foundry is an open, multi-vendor platform is very nice because it helps us avoid the dangers of vendor-locking and the related costs. Another reason: It also has multi-language support, including Ruby, Java, Scala, and NodeJs; and it offers many services, from relational stores such as MySQL and PostgreSQL, to queues like RabbitMQ, to N oSQL storage like MongoDB and Redis. Another big advantage is that it integrates very nicely with Spring. These things combined make Cloud Foundry a very interesting platform. CloudFoundry.com, the VMWare-hosted version of Cloud Foundry, is still in beta at the time of writing. Nevertheless, you can sign up for it by going to https:llmy.cloudfoundry.com/signup and entering an e-mail address. After reading and agreeing with the Terms of Service, you can click the Request Invite button. You'll get an e-mail confirming your signup request. Later (it can take a few hours or even a day), you'll receive an e-mail with the credentials you need to actually deploy on CloudFoundry.com. That's all you need to do to register. Deploying Our Application In this section, we are going to describe how we can deploy the sample application on Cloud Foundry. We will describe each step in detail and also explain the modifications we must do to make everything work as expected. If you want to perform the actions described here yourself, we will assume that you have read the initial chapter on how to set up your environment. We are also assuming you have either STS or an Eclipse instance with the STS plug-in installed. Installing the Cloud Foundry Plug-in Although Cloud Foundry offers several tools to get your application deployed, the fastest way to get started when you first dive in is to use the Eclipse plug-in. The alternative is using the VMC command­ line application, which is implemented as a Ruby gem. An advanced user can't escape using the VMC command-line; but for the scope of this appendix, we'll use the Eclipse plug-in. • Note RubyGems6 is the package manager for Ruby. It is comparable to apt-get for Ubuntu or yum for Red Hat. A gem is a packaged Ruby application or library. You can find more info on the VMC install at http://start.cloudfoundry . com/tools/vmc/installing-vmc. html. If you have Ubuntu, you can also directly install the command-line client using apt-get install cloudfoundry-client. We'll start by installing the Cloud Foundry Eclipse plug-in. Go to the STS plug-in Dashboard (it can be found under Menu ~ Help ~ Dashboard), click the Extensions tab found on the bottom of the window, and search for cloud foundry in the search bar. Check the found extension, and then click the Install button on the bottom right, as seen in Figure A-I. 6http://rubygems.org 537 APPENDIX A • CLOUD FOUNDRY: DEPLOYING TO THE CLOUD , Dashboard 1::l =0 SprlngSource Tool Suite 4 spring Find: cloud foundry Show Installed Server and Clouds Support for Server and Clouds 6 Cloud Foundry Integration by VMware. Inc .• Free. Commercial <D The integration supports managing application deployments. service bindings and instance scaling on VMware Cloud Foundry find updates configure Extensions Install Dashboard Extensions Figure A -1. Finding the Cloud Foundry plug-in You'll get the normal plug-in installation windows that ask you to accept or reject the license agreement. Click the Next and OK buttons until you get a dialog asking you to restart Eclipse, and then choose to restart it by clicking Restart now. Now that we've installed the plug-in, we can proceed to the next step: deploying our application on Cloud Foundry. Making Some Adjustments The teams behind Spring and Cloud Foundry have worked at making it very easy to deploy Spring apps on Cloud Foundry. It is an explicit goal to make Spring applications deployable without changing one line of configuration or code in most cases. Unfortunately, this is not entirely true for our application because it will not get deployed without us making some changes. The main reason is that Cloud Foundry, at the time of writing, only provides a Tomcat 6 instance (support for Tomcat 7 is on the road map). The other driver for change is the way SSL is set up in Cloud Foundry, which has some impact on the way we configure Spring Security. 538 APPENDIX A • CLOUD FOUNDRY: DEPLOYING TO THE CLOUD Switching to Tomcat 6 Tomcat 6 is a Java EE5 servlet container, so it does not implement the Servlet 3 API. The local server instance we have been using so far is Tomcat 7, which is Java EE 6 compliant. Our sample applications have an explicit dependency on Java EE 6---and the Servlet 3 API in particular. Until now, we've been bootstrapping the Spring application context in BookstoreWebApplicationlni tializer, which is an implementation of org. springframework. web . WebApplicationlnitializer. The WebApplicationlni tializer mechanism is what allowed us to get by without using a web. xml fIle for so long; however, it depends on a Servlet 3 implementation to work.
Load more

Recommended publications
  • What Is Bluemix
    IBM Brings Bluemix to Developers! This document has been prepared for the TMForum Hackathon in Nice, France. The first section of this document shares Bluemix related notes, and it is followed by notes appropriate for viewing content from exposed APIs (provided by TMForum and FIware) then you see the node flows that are available for you. IBM® Bluemix™ is an open-standard, cloud-based platform for building, managing, and running apps of all types, such as web, mobile, big data, and smart devices. Capabilities include Java, mobile back-end development, and application monitoring, as well as features from ecosystem partners and open source—all provided as-a-service in the cloud. Get started with Bluemix: ibm.biz/LearnBluemix Sign up for Bluemix: https://ibm.biz/sitefrbluemix Getting started with run times: http://bluemix.net/docs/# View the catalog and select the mobile cloud boilerplate: http://bluemix.net/#/store/cloudOEPaneId=store Tap into the Internet of Things: http://bluemix.net/#/solutions/solution=internet_of_things Bluemix tutorial in Open Classroom: http://openclassrooms.com/courses/deployez-des-applications- dans-le-cloud-avec-ibm-bluemix This table below can be used for general enablement. It is been useful to developers are previous hackathons. Source Code : Quick Start Technical Asset Name URL/Mobile App Technical Asset Description Guide Uses Node.js runtime, Internet Connected Home Automation ibm.biz/ATTconnhome2 of Things boilerplate, Node-RED ibm.biz/ATTconnhome2qs App editor and MQTT protocol Uses Node.js runtime, Connected
    [Show full text]
  • Google App Engine
    Basics of Cloud Computing – Lecture 6 PaaS - Platform as a Service Google App Engine Pelle Jakovits 18 March, 2014, Tartu Outline • Introduction to PaaS • Google Cloud • Google AppEngine – DEMO - Creating applications – Available Google Services – Costs & Quotas • Windows Azure PaaS • PaaS Advantages & Disadvantages 2 Cloud Services 3 Platform as a Service - PaaS • Model of Cloud Computing where users are provided with a full platform for their applications • Enables businesses to build and run web-based, custom applications in on -demand fashion • Eliminates the expense and complexity of selecting , purchasing, configuring , and managing the hardware and software. • Provides access to unlimited computing power, decreasing upfront costs dramatically 4 PaaS Characteristics • Multi-tenant architecture • Built-in scalability of deployed software • Integrated with web services and databases • Users are provided with tools to simplify creating and deploying applications • Simplifies prototyping and deploying startup solutions 5 PaaS Characteristics • Users only pay for the service that they use. • More fine grained cost model • Provides tools to handle billing and subscription management • Using PaaS typically results in a vendor lock-in. 6 Types of PaaS • Stand Alone Application Platforms – Typically built on top of an existing IaaS – Provides development tools for designing and deploying software. – Provide all required computing resources and services needed for hosted applications • Social Application Development Platforms – Used to develop addons and internal applications for social websites like Google+ and Facebook. – Integrated API with the social website platform. – Can be seen as extending a SaaS • Open-Computing Platforms – Not tied to a single IaaS provider. – Supports applications that are written in numerous languages and that use any type of database, operating system, and server.
    [Show full text]
  • Openshift Vs Pivotal Cloud Foundry Comparison Red Hat Container Stack - Pivotal Cloud Foundry Stack
    OPENSHIFT VS PIVOTAL CLOUD FOUNDRY COMPARISON RED HAT CONTAINER STACK - PIVOTAL CLOUD FOUNDRY STACK 3 AT A GLANCE PIVOTAL CF OPENSHIFT • ●Garden and Diego • ●Docker and Kubernetes • ●.NET and Spring • ●.NET, Spring and JBoss Middleware • ●Only Cloud-native apps (including full Java EE) • ●Container security on Ubuntu • ●Cloud-native and stateful apps • ●Deployment automation • ●Enterprise-grade security on • ●Open Core Red Hat Enterprise Linux • ●Pivotal Labs consulting method • ●Complete Ops Management • ●100% Open Source 5X PRICE • ●Red Hat Innovation Labs consulting method BRIEF COMPARISON PIVOTAL CF OPENSHIFT GARDEN & DIEGO DOCKER & KUBERNETES • ●Garden uses OCI runC backend • ●Portable across all docker platforms • ●Not portable across Cloud Foundry distros • ●IP per container • ●Containers share host IP • ●Integrated image registry • ●No image registry • ●Image build from source and binary • ●Private registries are not supported • ●Adoption in many solutions • ●No image build • ●Adoption only in Cloud Foundry 11 NO NATIVE DOCKER IN CLOUD FOUNDRY Converters Are Terrible Cloud Foundry is based on the Garden container runtime, not Docker, and then has RunC and Windows backends. RunC is not Docker, just the lowest runtime layer Docker Developer Experience Does Not Exist in PCF PCF “cf push” Dev Experience does not exist for Docker. In Openshift v3 we built S2I to provide that same experience on top of native Docker images/containers Diego Is Not Kubernetes Kubernetes has become the defacto standard for orchestrating docker containers.
    [Show full text]
  • What Is Cloud Computing?
    Cloud Computing for Nonprofits Executive Summary Written by Afua Bruce February 2020 What is Cloud Computing? Cloud computing can be defined as the rental of someone else‘s computer resources to provide services — applications, infrastructure, security, software, and storage. There are three main categories of cloud computing: infrastructure as a service (IaaS), platform as a service (PaaS), and software as a service (SaaS). CATEGORY INFRASTRUCTURE AS PLATFORM AS A SERVICE SOFTWARE AS A SERVICE A SERVICE Abbreviation IaaS PaaS SaaS Cloud provider Provides the server Maintain system software, Deliver software through an internet responsibilities hardware and a small including upgrades and connection; maintain system amount of storage and patches; tools to manage software and databases; provision networking software to hardware and software user accounts and provide security host applications Example services Amazon Web Services Amazon Web Services (AWS) Office 365, Salesforce, Google Apps, (AWS) Elastic Compute Elastic Beanstalk, Heroku, Asana, Slack, Calendly, Hootsuite Service, Google Microsoft Azure, Cloud Foundry Compute Engine (GCE), Apache CloudStack, OpenStack Positives and Negatives of Cloud Computing The flexibility of cloud computing makes it attractive to nonprofits. As organizations grow or their needs change, rather than continually purchasing new storage capacity to support applications, by leveraging cloud computing, nonprofits can simply request additional space based on current needs and usage. As with all technology, however,
    [Show full text]
  • Annual Report 2018
    Annual Report 2018 January 2019 In 2018, the Foundation expanded its definition of Cloud Foundry, shifting away from prioritizing the Application Runtime in order to spread awareness of the many projects that comprise Cloud Foundry technologies. This new messaging aligned with the 2018 vision for interoperability, a theme that underpinned all Foundation content. The interoperability of Cloud Foundry was evident across the ecosystem -- in the technologies integrated into the platform itself to the technologies with which Cloud Foundry integrates to form a multi-platform strategy. This year, the Foundation launched a Certified Systems Integrators program, announced new Certified Providers Cloud.gov and SUSE, accepted interoperable projects Eirini and CF Containerization into the Project Management Council and published four research reports -- while planning and hosting two major Summits and six Cloud Foundry Days. Like the platform itself, the Cloud Foundry Foundation has reached a new level of maturity and continues to evolve. Cloud Foundry Foundation Annual Report 2018 2 2018 Highlights TECHNICAL & COMMUNITY • Interoperability: Two new projects were accepted by the Project Management Committees in order to further integrate Kubernetes with Cloud Foundry technologies. CF Containerization, initially developed and donated to the Foundation by SUSE, is designed to package Cloud Foundry BOSH releases into containers and deploy those containers into Kubernetes. Eirini, proposed by IBM and seeing contributions from IBM, SUSE and SAP, is working towards allowing operators and product vendors to use Kubernetes as the underlying container scheduler for the Cloud Foundry Application Runtime. • 2018 Certified Providers: In 2018, Cloud.gov and SUSE joined the list of certified providers of Cloud Foundry, bringing the total to eight -- the other six being Atos, Huawei, IBM, Pivotal, SAP and Swisscom.
    [Show full text]
  • Guide to the Open Cloud Open Cloud Projects Profiled
    Guide to the Open Cloud Open cloud projects profiled A Linux Foundation publication January 2015 www.linuxfoundation.org Introduction The open source cloud computing landscape has changed significantly since we published our first cloud guide in October 2013. This revised version adds new projects See also the rise of Linux container and technology categories that have since technology with the advent of Docker gained importance, and in some cases and its emerging ecosystem. You will be radically change how companies approach hard pressed to find an enterprise Linux building and deploying an open source distribution that isn’t yet working on Docker cloud architecture. integration and touting its new container strategy. Even VMware vSphere, Google In 2013, many cloud projects were still Cloud Platform, and Microsoft Azure are working out their core enterprise features rushing to adapt their cloud platforms to the and furiously building in functionality. And open source Docker project. enterprises were still very much in the early stages of planning and testing their public, This rapid pace of innovation and resulting private or hybrid clouds–and largely at the disruption of existing platforms and vendors orchestration layer. can now serve as a solid case study for the role of open source software and Now, not only have cloud projects collaboration in advancing the cloud. consistently (and sometimes dramatically) grown their user and developer Other components of the cloud infrastructure communities, lines of code and commits have also followed suit, hoping to harness over the past year, their software is the power of collaboration. The Linux increasingly enterprise-ready.
    [Show full text]
  • What .NET Developers Need to Know About Azure Contents Microsoft Azure: a History
    What .NET developers need to know about Azure Contents Microsoft Azure: A History ..................................................................................... 3 Shifting Perspectives for Microsoft Azure .................................................. 7 Impact on the Development Life Cycle ......................................................10 Introduction to the Latest Azure Innovations ...........................................14 01 Microsoft Azure: A History 3 Launched in January 2010, Microsoft Azure is now more than seven Azure has been through many rounds of changes that have significantly years old. Like all seven-year-olds, Azure has been through some affected the ways in which .NET and other developers interact with the memorable teething troubles over the years, as well as some incredible platform. growth and change. In this section, we’ll look back at the history of Microsoft Azure, including the ways in which Microsoft’s strategy for the The shift in strategy has been rocky at times. In 2011, technology reviewers platform and for the company as a whole have shifted in recent years. described Microsoft Azure as a confusing platform with a difficult to use Recently, Microsoft has focused on opening up the Azure environment web-based interface and incomprehensible documentation. Since then, to widen its appeal to all kinds of developers, including those working in the teams working on the platform have gradually improved it, resulting in non-Microsoft frameworks and languages. a much more user-friendly platform that offers a well-organized array of services. Microsoft’s History From the 80s to One of the biggest changes for the Microsoft Azure platform was its evolution from a Silverlight application to a web portal written in the new the 2000s HTML5 standard.
    [Show full text]
  • Cloud Foundry Installation Documentation Release 0.1
    Cloud Foundry Installation Documentation Release 0.1 Lumír Jasiok Sep 14, 2017 Contents: 1 Getting Started 1 2 OpenStack Installation 3 2.1 OpenStack Requirements........................................3 3 Glossary 5 4 Indices and tables 7 i ii CHAPTER 1 Getting Started Using this documentation you should be able to deploy Cloud Foundry in easy and (mostly) automated way. First things first. Please read Glossary to be familiar with terminology and return back. Now, you have to clone repository with code to your computer. Go to the directory (of your choose) you created for Cloud Foundry deployment and run following code: git clone https://github.com/jas02/cloudfoundry-installation.git I am assuming, that you have installed Git. Now you should have in current directory sub-directory cloudfoundry-installation 1 Cloud Foundry Installation Documentation, Release 0.1 2 Chapter 1. Getting Started CHAPTER 2 OpenStack Installation OpenStack Requirements First, you have to ask your OpenStack administrator to create for you OpenStack project and credentials. Project should have at least following parameters: Hardware Requirements Instances VCPUs RAM Volumes Volume Storage 21 50 90GB 48 1.2TB Assign Floating IP and Create DNS Record To be allow access you Cloud Foundry instance from the outside OpenStack, you must have assigned Floating IP and create wildcard DNS record. To get Floating IP , you can use script in bin/cfi-assign-floating-ip.py in the cloudfoundry-installation repository directory. But before you can run the script, you have to cre- ate configuration file clouds.yaml and place it into the right directory. In case that you are using Linux, the directory is ~/.config/openstack.
    [Show full text]
  • Accelerate Application Development with Pivotal Cloud Foundry on AWS Focus on the Continuous Delivery of Custom Code, Not Maintaining Infrastructure
    Get started Accelerate Application Development with Pivotal Cloud Foundry on AWS Focus on the continuous delivery of custom code, not maintaining infrastructure Pivotal is an AWS Partner Network (APN) Advanced Technology Partner. Industry trends & challenges Remaining competitive in today’s business climate requires speed, agility, and quality, especially when it comes to the application development lifecycle. Legacy on-premises solutions are time consuming to maintain, update, and secure, which can expose corporate systems to bad actors. Moreover, they often entail expensive licensing that does not support continuous delivery or horizontal scaling. As a result, organizations are turning to the cloud for more flexible and agile operations with improved application availability, security, and total cost of ownership. The Pivotal Cloud Foundry Solution Pivotal Cloud Foundry on Amazon Web Services (AWS) is a cloud-native platform meant for building and running applications at scale. Using open source technology, PCF empowers organizations to rapidly and efficiently deliver new code. Pivotal integrates with a number of AWS services including Amazon Relational Database Service (Amazon RDS), Amazon Simple Storage Service (Amazon S3), Amazon DynamoDB, and Amazon Simple Queue Service (Amazon SQS), so teams can streamline the consumption of resources on the cloud. Benefits Pivotal Cloud Foundry on AWS enables companies to improve their application deployment lifecycle and accelerate their digital transformation. Developer Productivity High Availability Enable developers to quickly get their Keep your systems online during code into production with PCF’s modern the busiest times of year, with four tools and frameworks. layers of high availability built-in. Comprehensive Security Operator Efficiency Improve your security posture Increase productivity with built- with rapid patching and innovative in monitoring, logging, and credential management.
    [Show full text]
  • Magic Quadrant for Enterprise Application Platform As a Service, Worldwide 24 March 2016 | ID:G00277028
    Gartner Reprint https://www.gartner.com/doc/reprints?id=1-321CNJJ&ct=160328&st=sb (http://www.gartner.com/home) LICENSED FOR DISTRIBUTION Magic Quadrant for Enterprise Application Platform as a Service, Worldwide 24 March 2016 | ID:G00277028 Analyst(s): Paul Vincent, Yefim V. Natis, Kimihiko Iijima, Anne Thomas, Rob Dunie, Mark Driver Summary Application platform technology in the cloud continues to be the center of growth as IT planners look to exploit cloud for the development and delivery of multichannel apps and services. We examine the leading enterprise vendors for these platforms. Market Definition/Description Platform as a service (PaaS) is defined as application infrastructure functionality enriched with cloud characteristics and offered as a service. Application platform as a service (aPaaS) is a PaaS offering that supports application development, deployment and execution in the cloud, encapsulating resources such as infrastructure and including services such as those for data management and user interfaces. An aPaaS offering that is designed to support the enterprise style of applications and application projects (high availability, disaster recovery, external service access, security and technical support) is enterprise aPaaS. This market includes only companies that provide public aPaaS offerings. Gartner identifies two classes of aPaaS: high-control, typically third-generation language (3GL)-based and used by IT departments for sophisticated applications such as microservice-based applications; and high-productivity, typically model-driven and used either by IT or citizen developers for standardized application patterns such as those focused on data collection and access. Vendors providing only aPaaS-enabling software without the associated cloud service — cloud-enabled application platforms — are not considered in this Magic Quadrant.
    [Show full text]
  • UAA Presentation
    Identity@CF User Account and Authentication Agenda ▪ Who we are ▪ What we build ▪ Why it’s important ▪ How to use it CloudFoundry ▪ Open Source PaaS (Platform as a service) ▪ Multiple framework support - Java, Ruby, Node, Scala ▪ Multiple application services – MySQL, Postgres, Mongo, Redis, Rabbit ▪ Cloudfoundry.org ▪ https://github.com/cloudfoundry ▪ Cloudfoundry.com – Cloudfoundry service hosted by Vmware ▪ Other cloudfoundry instances are hosted by AppFog, ActiveState and Tier3 Who we are ▪ Identity team ▪ Dale Olds ▪ Dave Syer ▪ Luke Taylor ▪ Joel D’sa ▪ Vidya Valmikinathan [email protected] What we build ▪ UAA – User authentication and authorization server ▪ Spring Security Oauth2 – Spring project that supports UAA features ▪ uaac – Command line api client for the UAA ▪ Authentication servers to support ▪ External authentication sources (google, yahoo, github, linkedin), ▪ Enterprise identity - SAML2 Why is it important ▪ Higher degree of trust – Credentials are accepted only by a trusted source ▪ Standards based – Consistent, proven API, process and interactions that users are comfortable with ▪ Trustworthy interactions between the user and the platform ▪ Trustworthy interactions between components ▪ Simple third party participation to extend the platform Traditional approach to authentication Provides credentials Ok / Not Ok Checks user database User Server Oauth2 authorization code flow Who is this user What is he/she requesting Do I have the necessary authorization Present token with granted Accesses a client Client scopes
    [Show full text]
  • What Is Paas?
    WHITE PAPER What Is PaaS? How Offering Platform as a Service Can Increase Cloud Adoption WHY YOU SHOULD READ THIS DOCUMENT This white paper is about platform as a service (PaaS), a group of cloud-based services that provide developer teams with the ability to provision, develop, build, test, and stage cloud applications. It describes how PaaS: • Creates demand for and broadens adoption of cloud services across your organization by making it easier for developers to make applications available for the cloud • Unleashes developer creativity so that the focus is on creating innovative value-added services rather than the complexity of design and deployment • Facilitates the use of cloud-aware design principles in applications that make it simpler to move to a hybrid cloud model • Provides an ideal platform for developing mobile applications for multiple platforms and devices • Offers a strategic option for your organization by following six steps for planning Contents 3 Unleashing Developer Creativity Drives Demand for Cloud Services 5 PaaS: A Cloud Layer for Application Design 8 Developing for the Cloud 11 Planning for PaaS in Your Organization Unleashing Developer Creativity Drives Demand for Cloud Services As cloud technology continues to mature, more and more Plus, developers like using PaaS. According to Forrester’s businesses are offering cloud services to a broad constituency Forrsights Developer Survey, Q1 2013, the top reason developers across the organization. Typically, the service offered is turned to the cloud to build their applications is speed of infrastructure as a service (IaaS), one of three potential layers development, followed closely by the ability to focus of service in the cloud.
    [Show full text]