LOG.debug: SAML page requested, but samlData seems empty.

[lulumedic-loki]

Debug mode

• [X] I have enabled debug mode
• [X] I have read checked the Common Issues page

Describe the bug

[Okta Saml Settings] Single sign-on URL : https://snipeit.temp.co.kr/saml/acs Audience URI (SP Entity ID) : https://snipeit.temp.co.kr Default RelayState : Name ID format : I had tried both Name ID Format Unspecified and EmailAddress. Application username : I had tried both Application user name Okta username prefix and Okta username

[Snipe it Settings] Attribute Mapping - Username : I had tried both Attribute Mapping userName and Blank and EmailAddress

reference : Version v7.0.4 - build 14011 (master)

I am finding this very difficult and would like to seek help.

Reproduction steps

1. okta saml settings
2. snipe it samal settings
3. okta > snipe it saml login fail " Error: There was a problem signing in, please try again."

Expected behavior

Name ID format issue or version issue... ?

Screenshots

Snipe-IT Version

Version v7.0.4 - build 14011 (master)

Operating System

AWS Linux and Docker compose

Web Server

Docker compose

PHP Version

8.1.2-1ubuntu2.17

Operating System

macOS Sonoma 14.3.1

Browser

chrome

Version

No response

Device

No response

Operating System

No response

Browser

No response

Version

No response

Error messages

No response

Additional context

No response

[welcome[bot]]

👋 Thanks for opening your first issue here! If you're reporting a 🐞 bug, please make sure you include steps to reproduce it. We get a lot of issues on this repo, so please be patient and we will get back to you as soon as we can.

[lulumedic-loki]

Issues when posting using Docker Compose in 7.0.4

• Users not deleted after creation
• Unable to change back after changing language
• SAML integration not possible

Current version 6.0.0 All issues resolved

[snipe]

@lulumedic-loki That debug message is really just noise and can be ignored. The first and last have already been discussed here and we've already implemented workarounds. Just grab the latest image and use the workaround for SAML mentioned in the issue (add baseurl=https://assets.example.com/saml/ to your SAML Custom settings).

I cannot reproduce the language issue - can you reproduce on the demo?

[snipe]

Hi there - We haven't heard back in a bit, so I'm going to close this ticket for now, but will re-open it if you're still having issues.