adding logger component

[nip1904]

Hi, I was wondering if it would be possible to enhance the SQLPage application by adding a log feature that allows user to log text to underlying logger.

Something like

select
	'log' 	as component,
	'info' 	as priority,
	'test'	as output;

results in:

[2025-08-07T07:29:04.026Z INFO actix_web::user::logger] test

I want to use it for debugging output or if OIDC login for a user fails.

[lovasoa]

Hello !
Making such a component is definitely possible, but I'm not sure how it would help you debug oidc issues. Can you describe the issues you are facing in a little bit more details ?

The oidc flow is executed before any sql runs, so I'm not sure such a logging component would help. Can you tell us a little bit more about how you would use it ?

[nip1904]

Hi,

you got me wrong. (it was an or).

example for oidc
[2025-08-07T07:29:04.026Z INFO actix_web::user::logger] user bob ist not allowed to login

example for a debug (nothing to do with oidc)
[2025-08-07T07:29:04.026Z INFO actix_web::user::logger] json output from test,sql: {"item": "orange"}

[lovasoa]

Could you give a few concrete examples of how you would use such a components ? Situations where you think it would be helpful ?

For instance, if an oidc login fails, the user is redirected without any of your sql executing, so a new component would not help you in that situation. You could not create a message like user bob ist not allowed to login

[nip1904]

ok, i'll try to explain

authn is done via OIDC (keycloak in my project)

when it comes to authz it will be my app to allow or deny based on token claims

let say:

user has claim {"app_role": "user"}

admin has claim {"app_role": "admin"}

I have two folder - both with activated oidc

/user/index.sql vs /admin/index.sql

i will for claim like so

-- authz user
set needed_role = 'user'
set user = (select lower(sqlpage.user_info('username')));
set has_role = (select $user as value from json_each(sqlpage.user_info('app_role')) where value = $needed_role);

-- authz admin
set needed_role = 'admin';
set user = (select lower(sqlpage.user_info('username')));
set has_role = (select $user as value from json_each(sqlpage.user_info('app_role')) where value = $needed_role);

in the index.sql I will have

-- 403
select
    'redirect'  as component,
    '/403'      as link
where
    $has_role is null or $has_role <> $needed_role;

in /403.sql (no oidc activation)

set user = (select lower(sqlpage.user_info('username')));


--
SELECT 'status_code' as component, 403 as status;

--
select
    'alert'                                                                 as component,
    'Alert'                                                                as title,
    'alert-circle'                                                       as icon,
    'red'                                                                  as color,
    TRUE                                                                 as important,
    FALSE                                                                as dismissible,
    'You are NOT allowed to use this Interface!'    as description,
    'index.sql'                                                         as link,
    'Back to home'                                                 as link_text;
	
-- hopefully new
select
   'log'							  as component,
   '403 - failed ' || coalesce($user, 'None') as output,
  'error'							  as priority;

[lovasoa]

That's clear, thank you !

[lovasoa]

This is a valid use case, I'm open to adding this to sqlpage !

Would you be interested in submitting a pull request implementing this ? You could hook into https://github.com/sqlpage/SQLPage/blob/main/src/render.rs