arrodriguez

### Keybase proof

I hereby claim:

  * I am arrodriguez on github.
  * I am arrodriguez (https://keybase.io/arrodriguez) on keybase.
  * I have a public key ASATxXrJ1H-K_rkpfjnedb0KUhVGYmExPZamrhK22Wpsggo

To claim this, I am signing this object:

arrodriguez

Keybase proof

I hereby claim:

• I am arrodriguez on github.
• I am arrhrodriguez (https://keybase.io/arrhrodriguez) on keybase.
• I have a public key ASDpaKmBnre-hHmraUARIPUUrHF86Wh-0wu-M4BYli6Q_Ao

To claim this, I am signing this object:

arrodriguez

Secure Json

Objetivo

El objetivo de secure json es proveer un mecanismo de seguridad e integridad de los objetos json devueltos por nuestras apis con enfasís en el acceso público. Cada petición o respuesta SJSON debe ser declarada en la definición SWAGGER de la api publicada.

Hay varios casos de uso en donde SJSON se puede utilizar:

1. Mantener la seguridad y la integridad de los datos en una transacción "monetaria" pública.
2. Asegurar que las peticiones y respuestas REST no sean manipuladas por un atacante.

arrodriguez

In your local clone of your forked repository, you can add the original GitHub repository as a "remote". ("Remotes" are like nicknames for the URLs of repositories - origin is one, for example.) Then you can fetch all the branches from that upstream repository, and rebase your work to continue working on the upstream version. In terms of commands that might look like:

Add the remote, call it "upstream":

git remote add upstream https://github.com/whoever/whatever.git

Fetch all the branches of that remote into remote-tracking branches, such as upstream/master:

git fetch upstream

arrodriguez

{
    "id": 25418135,
    "repository": {
        "id": 2372423,
        "name": "travis-ci-webhook-receiver",
        "owner_name": "connexio-labs",
        "url": "https://github.com/connexio-labs/travis-ci-webhook-receiver"
    },
    "number": "6",
    "config": {