I am testing out JIT as instructed in <https www gooddata co GoodData #gooddata-cn

I am testing out JIT as instructed in <https://www...

Dongfeng Lu

10/16/2024, 3:52 PM

I am testing out JIT as instructed in https://www.gooddata.com/docs/cloud-native/3.7/manage-organization/set-up-authentication/. The first thing I thought when I saw "JIT ID Token Example" is, how do I check? In what log can I see it? As I searched logs for GDCN micro services, I noticed the logging level is probably set to "INFO". How do I set them to DEBUG if needed, as I suspect that the JIT ID Token may be there in DEBUG mode? Do I need to set it up individually to each deployment or statefulset? Is there a global setting for all GDCN deployments?

Jan Kos

10/17/2024, 7:36 PM

Hi Dongfeng, this is not something we are logging in CN application. Inspecting ID token needs to be done on an Identity provider side, as this is where the ID token is generated during OIDC login flow.

Dongfeng Lu

10/17/2024, 7:40 PM

Hi Jan. That is fair. But can you answer my questions about changing logging levels if it is available? Thanks.

Jan Kos

10/17/2024, 7:41 PM

Sure, let me check it internally.

Jan Kos

10/21/2024, 1:27 PM

Hi setting DEBUG loglevel needs to be set per deployment and per microservice to some degree. For java microservices, you’d need to add (not replace)

-Dlogging.level.root=debug

jvmOptions

e.g.

Copy code

jvmOptions: >-
  -XX:+ExitOnOutOfMemoryError -XX:+UseG1GC -Xss384k -XX:+UseStringDeduplication
  -XX:MinHeapFreeRatio=15 -XX:MaxHeapFreeRatio=25 -XX:AdaptiveSizePolicyWeight=50
  -XX:InitiatingHeapOccupancyPercent=25 -XX:GCTimeRatio=25 -XX:CompressedClassSpaceSize=32M
  --add-opens=java.base/sun.net=ALL-UNNAMED --add-opens=java.base/java.lang=ALL-UNNAMED 
  --add-opens=java.base/java.nio=ALL-UNNAMED -Dlogging.level.root=debug

For Quiver microservice 1. Part of helm charts is

quiver/config.yaml

2. In there, at the end is a section like this:

Copy code

quiver.logging.ini: |
    [loggers]
    keys = root, quiver

    [handlers]
    keys = quiver_stream_handler

    [formatters]
    keys = quiver_formatter

    [logger_root]
    level = INFO
    handlers = quiver_stream_handler

    [logger_quiver]
    level = INFO
    qualname = quiver
    handlers =

    [handler_quiver_stream_handler]
    class = StreamHandler
    level = DEBUG
    formatter = quiver_formatter
    args = (sys.stderr,)

    [formatter_quiver_formatter]
    format = %(message)s

This should be modified so to look like this:

Copy code

quiver.logging.ini: |
    [loggers]
    keys = root, quiver

    [handlers]
    keys = quiver_stream_handler

    [formatters]
    keys = quiver_formatter

    [logger_root]
    level = DEBUG
    handlers = quiver_stream_handler

    [logger_quiver]
    level = DEBUG
    qualname = quiver
    handlers =

    [handler_quiver_stream_handler]
    class = StreamHandler
    level = DEBUG
    formatter = quiver_formatter
    args = (sys.stderr,)

    [formatter_quiver_formatter]
    format = %(message)s

both

logger_root

and

logger_quiver

must be set to

DEBUG

. you can check helmchart values in https://artifacthub.io/packages/helm/gooddata-cn/gooddata-cn?modal=values

Dongfeng Lu

10/21/2024, 9:27 PM

Thanks, Jan, for the information. I will test it out later.

6 Views

Open in Slack

Previous Next