List<T> list = asList(strictlyOrderedElements);

    // for use calling Collection.toArray later
    T[] emptyArray = Platform.newArray(strictlyOrderedElements, 0);

    // shoot me, but I didn't want to deal with wildcards through the whole test
    @SuppressWarnings("unchecked")
    Scenario<T> starter = new Scenario<>((Ordering<T>) ordering, list, emptyArray);
    verifyScenario(starter, 0);
  }

    List<T> list = asList(strictlyOrderedElements);

    // for use calling Collection.toArray later
    T[] emptyArray = Platform.newArray(strictlyOrderedElements, 0);

    // shoot me, but I didn't want to deal with wildcards through the whole test
    @SuppressWarnings("unchecked")
    Scenario<T> starter = new Scenario<>((Ordering<T>) ordering, list, emptyArray);
    verifyScenario(starter, 0);
  }

Username: `johndoe`
Password: `secret`

/// check | "確認"

コードのどこにも平文のパスワード"`secret`"はなく、ハッシュ化されたものしかないことを確認してください。

///

<img src="/img/tutorial/security/image08.png">

エンドポイント`/users/me/`を呼び出すと、次のようなレスポンスが得られます：

```JSON
{
  "username": "johndoe",
  "email": "******@****.***",
  "full_name": "John Doe",
  "disabled": false
}
```

xrŽûÀxi`juOªszin滸Ē*˜' ¾ qjD ¦¼aÜc¥®ºImW M}ò²CsG¢xcÐtslôwWHªCY÷QKph¸Vñú}n18ôO¢ebv®VÖILxgk !iaxm„V_ÚÅ@GM[LÏû>TU\rÉ”°¡Çó eTi[¦oñwwýznˆ^q ãZfYI^KuoïuWˆLñˆNñ~Lª ˜´‚òÔà~DÕpÌ_ZZKxP]Õ²«ƒŽ 6/¼’©z rgLˆ7í~L# ܈• ¸¾“t - ¬è UoV|k±k„q~ÜqzRGW¸NïON DB@FHbÚÆ ñncE²{¥me `r IxGJ~KÕ>kv\¢¯req£¯Îéü >)Þê)i noŠÐQrVy²HITqIò{¼L~so¸ ˜ Š²@c¾ ºµ‚®Ð^`dD_V^iLzKdlwÕº¥ ² ° ,ª«Ð²tåB†7“fVoLFª—˜š˜ £€‘¸ …`Šƒ! , öWwNÚaws²eÐPGxnïUºDsGBýptÜdxj@Ä·¹²"oÕB¬ it ¸…UxRqåNg|SVIÖBqq¥ <IEˆ¤{_UòC¼ gT3 ¸ ñhGmfq Ú3q\› ¼ GTBwÖºwmeqˆqyX`ªýh²sex»llo¸t1...

```

#### Docker Cache

There's an important trick in this `Dockerfile`, we first copy the **file with the dependencies alone**, not the rest of the code. Let me tell you why is that.

```Dockerfile
COPY ./requirements.txt /code/requirements.txt
```

?v&ats?el??y&oh?øh???ivsgnok??il?jkniets?k&a&nvej?rem?s&gnir?nellu???ie-er&den?v&o?ø???ram?sa?årem??la&jf?vh??m&b&ah?áh??mahellil??nnul?ts&l&oj?øj??ul??y&o?ø???imp&ah?áh??m!.sg??osir?t!.sg??ádiáb?ævsyt?øsir??s&adnil?en&dnas?e&dga?k&ri&b?k??som??ve??me&h?jg??nroh-go-ejve?s&a?ednil?k&o?ø??of?yt?å??tsev??gv?hf?igaval?o&r&or?ør??sman??so&fen&oh?øh??m?v??uh&lem?sreka.sen??å!dnil???t&a&baol?g&aov?grav??jjr&av-attam?áv-attám??l&a&b?s??ás??soum?ts?v&eib?our???e&dnaly&oh?øh??f?s&nyt?rokomsdeks?sen??vtpik...

?v&ats?el??y&oh?øh???ivsgnok??il?jkniets?k&a&nvej?rem?s&gnir?nellu???ie-er&den?v&o?ø???ram?sa?årem??la&jf?vh??m&b&ah?áh??mahellil??nnul?ts&l&oj?øj??ul??y&o?ø???imp&ah?áh??m!.sg??osir?t!.sg??ádiáb?ævsyt?øsir??s&adnil?en&dnas?e&dga?k&ri&b?k??som??ve??me&h?jg??nroh-go-ejve?s&a?ednil?k&o?ø??of?yt?å??tsev??gv?hf?igaval?o&r&or?ør??sman??so&fen&oh?øh??m?v??uh&lem?sreka.sen??å!dnil???t&a&baol?g&aov?grav??jjr&av-attam?áv-attám??l&a&b?s??ás??soum?ts?v&eib?our???e&dnaly&oh?øh??f?s&nyt?rokomsdeks?sen??vtpik...

```

#### Cache Docker

Existe um truque importante nesse `Dockerfile`, primeiro copiamos o **arquivo com as dependências sozinho**, não o resto do código. Deixe-me te contar o porquê disso.

```Dockerfile
COPY ./requirements.txt /code/requirements.txt
```

         * the way we have been doing that is to call exists() which
         * calls this method so another technique will be necessary
         * to support DFS referral _to_ Win95/98/ME.
         */

        if( tree.session.transport.hasCapability( ServerMessageBlock.CAP_NT_SMBS )) {

            /*
             * Trans2 Query Path Information Request / Response
             */

§EcBSizeÒ §EcIndex ¦EcDistœ ¨CSumAlgo ¨PartNums‘ ©PartETagsÀ©PartSizes‘Ñ ªPartASizes‘Ñ ¤SizeÑ ¥MTimeÓ É Ÿ ²€§MetaSys ¼x-minio-internal-inline-dataÄ true§MetaUsr‚¤etagÙ 14a1119d5fe668d77000¬content-type¸application/octet-stream¡v ΙøÍ‘ ¤nullÄ7 ÙÉ ‹§>˜E° eò£mé$Q*9} ãŠD ð-j × ÿÿÿÿ%Í5ø "ð½Õ7VÏu}Ì­ ej multisitea/data/disterasure/xl9/.minio.sys/buckets/.background-heal.json/xl.meta XL2 Æ o Ä$•Ä Ó É žY'XÄ ÔxoG Å Cƒ¤Type ¥V2ObjÞ ¢IDÄ ¤DDirÄ ü `LΓA ³I*rfe ¦EcAlgo £EcM £EcN §EcBSizeÒ §EcIndex ¦EcDistœ ¨CSumAlgo...