Glenn Matthews

Working with SAML as well: ``` 14:02:07.534 INFO django.server : "GET /login/?next=/dcim/devices/%3Fstatus%3DActive HTTP/1.1" 200 33833 14:02:10.935 INFO django.server : "GET /login/saml/?next=/login/%3Fnext%3D/dcim/devices/%253Fstatus%253DActive&idp=azure HTTP/1.1" 302 0 14:02:11.512 INFO nautobot.auth.login signals.py user_logged_in_signal() :...

I don't *think* there have been any significant changes here in 2.x but I'll try to find time to retest with 1.6 just to be sure.

Behavior appears identical in 1.6.22.

Thank you @jdueitt - that's the best kind of bug report, one that already has a fix ready! 😃

The celery_worker startup errors should be fixable by changing the docker-compose so that it has: ```yaml depends_on: nautobot: condition: service_healthy ``` so that it doesn't attempt to start up while...

@NetOpsChic That specific error suggests that you're trying to run a newer version of Nautobot (2.x) in a docker container that was built for an older version (1.x), as the...

Can you give some examples of use cases where you'd want the template to "force" this behavior, rather than giving the user the option to select "Open link in new...

Blocked by #178.

As mentioned in the Slack thread, I'm currently pointing the finger at `'Network'` as an incorrect value coming from somewhere - it should be `PrefixTypeChoices.TYPE_NETWORK` (== `'network'`) instead.

Appears to be due to an unintended change in the `Job().name` value in Nautobot 2.2.3. We'll see about restoring the pre-2.2.3 behavior.