Hello everyone, On this matter I have already enquired with regards of Jenkins Core to have a fallback mechanism and I have been advised to address this issue at the SAML plugin level so that developers of Jenkins core don't have to reinvent the wheel with new features in the various authorisation plugins.
Long story short.... I have recently rolled out a Jenkins instance federated into ADFS via https://github.com/jenkinsci/saml-plugin. Everything works as supposed to with the exception of a local admin service user i.e. service-admin which is used for maintenance and configuration tasks hitting the http://127.0.0.1/cli endpoint. Yes, I'm aware that I could generate a token for service-admin user and use https://www.jenkins.io/doc/book/system-administration/authenticating-scripted-clients/ Unfortunately due the current setup I cannot use a user associated with a token. Therefore I'm here to enquire whether there are any plans to include the user fallback capability as already been implemented into active-directory-plugin https://plugins.jenkins.io/active-directory/ also in SAML plugin. I do apologise in advance for the similarities of posts. Regards, Phillip -- You received this message because you are subscribed to the Google Groups "Jenkins Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-users+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-users/73e0507a-8f06-e911-bf17-2cd5477a9b3f%40bailey.st.
