Is there a way to disable some of the settings pages?

[Loqova]

I tried simply blocking the pages already but that doesn't work I guess authenticate referes to some block I cannot include such requests in. I can probably disable it with a custom theme in the frontend but Im still searching for the locatino of those theme files inside the container. And I want to disable those functions in the backend too.

http://auth.xxxxxx.xx {
  respond /settings/sshkeys "Not accessible" 403 
  respond /settings/gpgkeys "Not accessible" 403 
  respond /settings/apikeys "Not accessible" 403 
  respond /settings/connected "Not accessible" 403

  authenticate with myportal
})

[greenpau]

@Loqova , I am actually working on the redesign of the settings page. May incorporate new features. What is the intent behind disabling the pages? Why did you choose to disable these particular pages?

[Loqova]

I didn't disable it but wanted to. What I tried didn't work. For the sake of customizability. I have several use cases where I would only want to use this for simple auth + mfa without the ssh/gpg/api/connected features.

[greenpau]

I didn't disable it but wanted to. What I tried didn't work. For the sake of customizability. I have several use cases where I would only want to use this for simple auth + mfa without the ssh/gpg/api/connected features.

@Loqova , makes sense. Will think how to enable/disable features.

[greenpau]

I will be adding the following directive to Caddyfile:

authentication portal myportal {
  ui {
    disable settings [gpgkeys|sshkeys|apikeys|connected|mfa|password|general]
  }
}

By default all sections of the "Settings" page are enabled. If disabled, then the section will not be visible in the UI.

[Loqova]

Great, thanks a lot. Is it only disabled in the UI? Therefore, would calling the functions directly still work? As that seems kind of insecure to me.

[greenpau]

@Loqova , it will be disabled everywhere.