kevprice83

PS C:\Users\kpric> crc start -p C:\Users\kpric\Downloads\pull-secret.txt --log-level "debug"
DEBU CodeReady Containers version: 1.14.0+36ad776
DEBU OpenShift version: 4.5.4 (embedded in binary)
DEBU Total memory of system is 34249129984 bytes
DEBU No new version available. The latest version is 1.14.0
INFO Checking if oc binary is cached
DEBU Running 'C:\Users\kpric\.crc\bin\oc\oc.exe version --client'
DEBU oc binary already cached
INFO Checking if podman remote binary is cached
DEBU Currently podman remote is not supported

kevprice83

Using a public certificate with Red Hat Single Sign On

Context

When deploying Red Hat Single Sign On for a test or PoC, most users will choose to use a self-signed certificate as explained in the official documentation. The setup instructions are straightforward but this self-signed certificate will trigger certificate error messages in your web browser and can also prevent some clients such as Postman from working properly. This guide explains how to get a public certificate for Red Hat Single Sign On.

Are you using a public certificate ?

kevprice83

Steps to enable 3scale batcher policy

Follow the steps to download and modify the JSON config file for your gateway and then run the list of commands in OpenShift to enable the policy.

Modifying the JSON

• Download the specific version of the apicast config file required from the API manager.

curl -X GET "https://{TENANT_NAME}-admin.{WILDCARD_DOMAIN}/admin/api/services/{service_id}/proxy/configs/{environment}/{version}.json?access_token={access_token}" > apicast.json

kevprice83

Installing 3scale AMP2.1 on EC2

You will need:

• a running instance with 8GB RAM minimum (recommended 16GB) and RHEL

• <PUBLIC_DNS>: (e.g. ec2-54-123-456-78.compute-1.amazonaws.com)

• ``: (e.g. 54.123.456.78)

kevprice83

Dynamic 3scale Developer Portal signup templates

There are 4 custom signup flows included in the parent homepage. These flows are included into the homepage using Liquid tags such as {% include 'partial name' %} because the flows are separated out into individual partials. The partials can be included in your 3scale portal individually or all together depending on which flows you want to enable in your portal and for ease of switching between flows as and when needed.

NOTE: If you prefer you can create a separate page to render the subscription forms to the different Services. This would be particularly useful if you want to allow multiple applications per account for the Custom Field & Group Membership Flows.

How does the 3scale signup work?

The Basics

A developer can sign up to subscribe to an API service in various ways

kevprice83

How this works

This solution is based on a custom HTTP header being passed with all client requests, the value of that header should be the equivalent of the matching metric system name configured in 3scale.

This customisation has been tested with the following image of APIcast:

• registry.access.redhat.com/3scale-amp20/apicast-gateway

kevprice83

What is this?

• This gist is a solution to build a developer portal in 3scale with a workflow that allows signup to services based on the scope of the user.
• The template have been adapted from the default index.html page.
• This solution is dependent on the correct settings being configured in the 3scale admin portal & the users being scoped by means of the Groups feature.
• The Service Plan Features have been used in this solution instead of the Service system_name.

kevprice83

RH SSO installation & configuration

download rhsso from https://access.redhat.com/jbossnetwork/restricted/softwareDownload.html?softwareId=44851

• unzip rh-sso-7.0.0.zip
• ./add-user-keycloak.sh -u <username>
• From the directory rh-sso-7.0 execute bin/standalone.sh This will start up the sso instance
• To expose the console on a public domain follow the next steps
• wget https://bin.equinox.io/c/4VmDzA7iaHb/ngrok-stable-linux-amd64.zip
• unzip ngrok-stable-linux-amd64.zip

kevprice83

{
    "swagger": "2.0",
    "schemes": [
        "http",
        "https"
    ],
    "host": "petstore.swagger.io",
    "basePath": "/v2",
    "info": {
        "description": "This is a sample server Petstore server.\nYou can find out more about Swagger at\n[http://swagger.io](http://swagger.io) or on [irc.freenode.net, #swagger](http://swagger.io/irc/).\nFor this sample, you can use the api key `special-key` to test the authorization filters.\n# Introduction\nThis API is documented in **OpenAPI format** and is based on\n[Petstore sample](http://petstore.swagger.io/) provided by [swagger.io](http://swagger.io) team.\nIt was **extended** to illustrate features of [generator-openapi-repo](https://github.com/Rebilly/generator-openapi-repo)\ntool and [ReDoc](https://github.com/Rebilly/ReDoc) documentation. In addition to standard\nOpenAPI syntax we use a few [vendor extensions](https://github.com/Rebilly/ReDoc/blob/master/docs/redoc-vendor-extensions.md).\n# OpenAPI Specification\nThis API is documented in **Open

kevprice83

{
      "kind": "ImageStream",
      "apiVersion": "v1",
      "metadata": {
        "name": "redis",
        "annotations": {
          "openshift.io/display-name": "Redis"
        }
      },
      "spec": {