JAAS security with Open Liberty

オープン
#3,359 コメント 3 件 リアクション 0 件 担当者 0 名 GitHub で見る

メンテナーはふだん 1 日以内に返信

まだ誰も着手していません。

評価

難易度
5/5
見積もり時間
1週間以上
初心者へのやさしさ
25/100
issue の種類
ドキュメント
明瞭さ
おおむね明確
活発さ
停滞
技術スタック
java

調査の方向性

まず、KC Authentication トピックに記載されている JAAS セクションを既存の OL Authentication トピックと比較し、有用性と範囲について Ajay および security SME と検討してください。妥当であれば、関連する JAAS の内容を扱う一貫した Open Liberty トピックを作成し、高度な詳細は限定し、すべてのガイダンスを cloud/container 環境での使用を前提として記述してください。

索引モデルが issue の本文から書いたものです。

説明

content design needed medium priority

From discussion with Alasdair when reviewing KC.

The KC Authentication topic contains a bunch of randomly-organised sections about different authentication-related things. Several of them relate to JAAS (Java SE security) but they're spread around without a coherent flow.

Talk with Ajay about whether it's useful info for us to provide or whether that info is covered by the short paragraph and links to elsewhere that are in the [OL Authentication topic]https://www.openliberty.io/docs/latest/authentication.html#_jaas_authentication) already.

If he thinks it's necessary, and there's enough info needed that it's worth a whole topic, create a single OL docs topic about JAAS security that pulls together the information from the following sections of the KC Authentication topic:

  • JAAS configuration
  • JAAS login modules
  • Callback handler - don't do a lot on this because it's quite internal and advanced use cases - callback handler is called by login module to get info needed (eg a username and pw prompt put up on screen) but, in reality, because this is server-side it often doesn't results in human interaction; human interaction is generally designed around client-side stuff.
  • Pluggable authentication
  • Proxy login module
  • Hash table login module
  • Identity assertion - this one is something that a user raised an RFE about fairly recently because they wanted to log in people using just a user ID and no password (I think). But, it's an advanced use case and Alasdair doesn't know how much we need to talk about it - would need to ask the security team to provide solid use cases of when it would be needed (in a cloud/containerised context). As for everything in this list, check it's useful to more than just a handful of people in highly specialised contexts.

You'll need to understand a bit about each of these things to work out how to organise them and structure the topic. It's possible that there are other bits of info that would need adding to make it all make sense. In general, make sure that the security SME can explain how each of these things is relevant in a cloud/containerised context - it must be framed like that in the OL docs.

主要言語
言語のデータがありません
スター
14
フォーク
58
平均マージ
1時間
マージ済み PR(30日)
25

環境構築

はじめの一歩

  1. issue を最後まで読み、次にプロジェクトのコントリビューションガイドを読みます。
  2. 着手することを issue にコメントします — 二人が同じ作業をするのを防げます。
  3. リポジトリをフォークし、ブランチを切って変更します。
  4. issue 番号を参照したプルリクエストを送ります。

OpenLiberty/docs のほかの issue

OpenLiberty/docs の issue をすべて見る

似ている issue

Cloud の issue をもっと見る

新しい issue をメールで受け取る

初心者向けの GitHub issue を短くまとめたダイジェスト。