 (formerly Swagger Specification) is an API description format for REST APIs. An OpenAPI file allows you to describe your entire API, including:

Available endpoints (/users) and operations on each endpoint (GET /users, POST /users)

Operation parameters Input and output for each operation

Contact information, license, terms of use and other information

 is a set of open-source tools built around the OpenAPI Specification that can help you design, build, document and consume REST APIs. The major Swagger tools include:

 – browser-based editor where you can write OpenAPI definitions.

 – renders OpenAPI definitions as interactive documentation.

 – generates server stubs and client libraries from an OpenAPI definition.

 – browser-based editor where you can write and review OpenAPI and AsyncAPI definitions.

 – Java-related libraries for creating, consuming, and working with OpenAPI definitions.

 – standalone library for parsing OpenAPI definitions

 – provides a single, unifying structure for describing APIs across various description languages and serialization formats.

The ability of APIs to describe their own structure is the root of all awesomeness in OpenAPI. Once written, an OpenAPI specification and Swagger tools can drive your API development further in various ways:

 for your API. The only thing left is to implement the server logic – and your API is ready to go live!

 that lets your users try out the API calls directly in the browser.

Use the spec to connect API-related tools to your API. For example, import the spec to 

Every API definition must include the version of the OpenAPI Specification that this definition is based on:

The OpenAPI version defines the overall structure of an API definition – what you can document and how you document it. OpenAPI 3.0 uses 

 are 3.0.0, 3.0.1, 3.0.2, and 3.0.3; they are functionally the same.

The info section contains API information: title, description (optional), version:

description: Optional multiline or single-line description in[CommonMark](http://commonmark.org/help/) or HTML.

Next.js With Swagger 3 Setup

Digital wallets are becoming more and more popular as we move into the digital age. If you're not familiar with digital wallets, they are essentially a digital way to store your money and other digital assets. You can use digital wallets for a variety of purposes, such as paying for goods and services online, transferring money to other people, or even Just storing your digital money. 

A digital blockchain wallet provides numerous advantages over traditional wallets.

For one, digital blockchain wallets are much more secure since they are decentralized and spread across a network of computers. This makes it virtually impossible for hackers to steal your information or funds.

Another advantage of digital blockchain wallets is that they offer greater privacy. Since your data is not stored in a central location, it is more difficult for third parties to track your transactions.

Finally, digital blockchain wallets are very user-friendly and easy to use. Even if you are not tech-savvy, you can still easily manage your digital blockchain wallet with ease.

There are a few different ways to set up a digital wallet. You can use your social account, email address, or even a hot wallet such as Metamask. In this article, we will show you how to set up a digital wallet using Metamask. First, you will need to create an account with Metamask. Once you have created an account, you will be able to log in and access your digital wallet. You will then be able to add funds to your wallet and start using it right away. Thanks for reading and we hope this article has helped you learn how to set up a digital wallet using Metamask.

Custodial wallets are automatically generated for Social Login users when they perform actions that would require a wallet, but they do not have one connected yet. For creators, this involves minting (publishing) an NFT if they haven’t yet connected a personal (non-custodial) wallet. 

Custodial wallets are also required for anyone who purchases with a credit card on our site, even if they have a personal wallet connected

When you create a digital wallet, you are typically assigned a 12 or 24-word keyphrase. This is your private key that you own and manage. This private key acts as a recovery phrase if you lose your password or are locked out of your wallet for any reason. You must store this key in a safe and secure place. If you lose it, you will lose access to your wallet’s contents forever.

Best practices for storing your private keys:

. Many people never even type their private keys once. The most secure place for a private key is in the “cold storage” of the physical realm where something is offline.

. There is never any reason to give anyone your private key. Don’t do it.

. Don’t lose it or store it in a place where the material on which your private key is written could be compromised.

Getting Started With Digital Wallets

At some point, old software installed, just has to go away. The million dollar question is when.

After recently experience of having a legacy system for about 8 years too long that prompted me to blog on this topic. I've seen the impact first hand with regard to project timelines, business climate changes, and constant tickets to the help desk. Project managers constantly asking, "Why does it take longer every year to do something simple?". - Really?

“A legacy system is an old method, technology, computer system or application program that continues to be used, typically because it still functions for the users’ needs, even though newer technology or more efficient methods of performing a task are now available.”

Those who are making these technology decisions are not typically directly affected by them. They’re looking at out-of-pocket cost versus total cost of ownership. While this takes place, I’m more concerned with all the time involved to resolve the same repeatable problems along with trying to figure out an escape from the legacy prison. So what do I do? Just keep answering those same ridiculous rhetorical questions of "Why does it takes so long and why is it so difficult" with a calm soothing voice, "Because you incurred Technical Debt".

During the course of 8 long years of projects, the project team took shortcuts due to a variety of reasoning, such as lack of technical ability, pressure of meeting project deadlines, or just flat-out lazy. You can imagine over time, these poor decisions accumulate huge backlogs of inefficiencies that keep getting kicked down the road. At some point, Peter may not let you rob him while Paul needs an early payment.

While the cost of maintaining an old system may indicate that a change is needed, it is also possible to spend more than necessary on a new solution. We need solutions that help us stay competitive, however wasting money on software upgrades, can be unnecessarily as it increases Technical Debt. When the old systems can’t keep up with the business demands or changes, it's time to replace. In the absence of due diligence, it is not always clear which option of replacement or upgrade, is best.

Most replacement systems at minimum, need to provide marginal benefits over any legacy system being replaced to justify the cost. Poor legacy software replacement decisions happen when technology decisions are not aligned with business requirements and strategy. Have you had lunch with your Enterprise Architect lately?

So let's encourage our product owners to make conscious decisions on if the economics justifies the cost of the incurring technical debt. Not all technical debt needs to be repaid as one can live with issues on a product nearing end of its life. Just like your payment of financial debt, it is good stewardship to first repay the "high interest" technical debt. It is preferable that technical debt be repaid incrementally (like making a monthly mortgage payment) through use of practices such as peer reviews, refactoring, continuous integration, and automated testing.

So what's your strategy for technical debt prioritization on your portfolio prison? A general rule of thumb could be based on comparing the degree of current value of business capabilities against the degree of business value that the system fulfills for future business needs. This may not get you out of an early prison sentence, however maybe, just maybe, feeling liberated removes illusions of being in one.

“That which we manifest is before us; we are the creators of our own destiny. Be it through intention or ignorance, our successes and our failures have been brought on by none other than ourselves.”
― 

Prisoner of Legacy Systems

Where does it all start to get rocking with API Web Services?

The industry trends tells us that we must adapt to using more API type of strategies as it plays into the 

 (Internet of Things). It allows for a portable way of abstracting an IT function into a reusable tool with a bi-product of driving down future solution delivery cost.

Just imagine the conversation that the next time that favorite project manager of yours asks you how long it will take to build out an automated solution to warm up the CEO’s high priced fancy projector 1 minute upon office arrival within the parking deck…and you actually don’t laugh out loud this time.

My analogy for why API technology is important…It’s like you handing out the Halloween candy to kids yourself to ensure you have enough to give out rather than letting the kids take how much candy they think is needed and hog around the porch stairs. Next thing you know you’re turning your front porch lights off and explaining to your wife that some big kid dressed in a robbers outfit took all the candy then broke the flower pot walking away. Who Knew.

Why another interface? Limiting direct calls to platforms for data (

), elastic to business environment changes (

), and allowing for quick-to-market solution deliveries (

Below is my helpful checklist for getting an environment built and running (DevOps) for establishing Java API Web Services while understanding the key technology areas that support the products needed for getting started. People will sometimes use more advanced product that cost money whereas using these products eliminate license cost while still having a great support base.

, a set of programming instructions and standards for accessing a Web-based software application or Web tool. A company releases its API to the public so that other software developers can design products that are powered by its service

, is a syntax for storing and exchanging data. JSON uses JavaScript syntax, but the JSON format is text only, just like XML. A primary data format used for asynchronous browser/server communication.

, an Architecture Style by decoupling architecture of API’s from Business Logic with a stateless uniform interface. RESTful systems typically, but not always, communicate over Hypertext Transfer Protocol (HTTP) with the same HTTP verbs (GET, POST, PUT, DELETE, etc.) which web browsers use to retrieve web pages and to send data to remote servers

, the most common protocol for communication of digital content. In the case of API’s, it allows us to Get (Retrieve a resource), POST (Create a resource), PUT (Update a resource), DELETE (Delete a resource)

 as a foundation for all the technology to work together as this contains the libraries and execution layers. As of April 2015, the JDK 7 will no longer provide updates however Oracle is in the process of migrating users from Java 7 to Java 8 through the auto update feature which took place after the January 2015 CPU release.

First, download and installations the two components for getting started.

We need something we can interact with to write code or drag and drop using some sort of IDE. Eclipse is a very common tool for Java developers, to build Java EE and Web applications, including a Java IDE, tools for Java EE, JPA, JSF, Mylyn, EGit and others.

The Apache Maven is a tool that can be used for building and managing any Java-based project. This tool can be leveraged by Eclipse to store the developer projects.

Maven’s Objectives
Maven’s primary goal is to allow a developer to comprehend the complete state of a development effort in the shortest period of time

Tomcat 9 will be needed to serving up content via HTTP within a browser. This can run locally on your PC or on a virtual server.

"Apache Tomcat™ is an open source software implementation of the Java Servlet, JavaServer Pages, Java Expression Language and Java WebSocket technologies. It also is an open software developed by the ASF or Apache Software Foundation. Designed to broker the web-serving features of JavaServer Pages. Allows integration of servlets through Java Servlet technology."

"Developing RESTful Web services that seamlessly support exposing your data in a variety of representation media types and abstract away the low-level details of the client-server communication is not an easy task without a good toolkit. In order to simplify development of RESTful Web services and their clients in Java, a standard and portable

"Swagger is a simple yet powerful representation of your RESTful API. With the largest ecosystem of API tooling on the planet, thousands of developers are supporting Swagger in almost every modern programming language and deployment environment. With a Swagger-enabled API, you get interactive documentation, client SDK generation and discoverability"

The Java API Web Service Cheap Seats

 anymore acronym. That once known 25+ year old industry coined term has occupied my life since 2000. That terminology to me just doesn’t have that same Mew to it these days. Maybe we just need more "

The new tone of “Identity Governance“(

-Credit to Geoff), is stepping in as the new sheriff of the language marketing game. Kind of like what “Cloud” did with aggregating storage area network clusters with unused parking data spaces. No offense.

In this case it’s acceptable to gently speak that “G” word as it relates to preventing security breaches or the recent cleaver social engineering tactics against Verizon. Incorporating governance of enforcing identity security polices is not commonly practiced while it is being discovered as commonly important.

The basic principles I’m accustomed with is first ensuring a core Identity is bound to personal identifiable information (PII) from an HCM system that can be authorized by a centralized Identity Store. Just create them an easy to remember ID and password then tell them not to share it with anyone. Of course it’s abstracted through a REST Web Service over encrypted and authorization channels - Oracle API Gateway is a cool tool for that!

Secondly, which Steve Jobs would argue as first, is allowing the user to have the ultimate friendly experience with a rich set of self-service controls and of course secure. Ever used online sites that limit the usability with creating “Logins” or “Accounts” to gain access to their site? They may have enforced you to select 1 of many bad questions to answer? Password Reset time…Who can really remember what street their grand-parents grew up or what you did on new years of 2000?

Where’s ole’ SAML 2.0 hiding? It’s still around and kicking while I see the concept of federation dangling, just not the protocol. What’s really become fascinating to watch is how the big social sites are leveraging next generation protocols like 

 for authentication of the “one login” approach. The idea is authenticating your access from third-party identity providers into a remote system (service provider) without traditional credentials like a username/password. It’s really convenient for registration of sites too when you’re not asked to fill in those long sets of questions. What about that dreaded messages “Sorry, that username is in use”? I know…this has been around since 2006 however the “mobility first” mentality has only taken off in the past couple of years. Especially since we now wear them on our wrists to bed to monitor our sleep patterns or to never miss that call again.

Need an easy two factor approach? I personally use a tool called “

” for authentication to my web sites which allows me to never use an ID or Password again. Just enter a 4 digit pin (

Does your Identity Management Platform need more cowbell?

Identity Management (IdM) the ‘It Doesn’t Mew’ anymore acronym

My

Blog and Tutorials

Next.js With Swagger 3 Setup

Getting Started With Digital Wallets

Prisoner of Legacy Systems

The Java API Web Service Cheap Seats

Need more Cowbell