SSO error after migration to 3.5.10

Hi after Migration to 3.5.10, problem at login.

The above exception was the direct cause of the following exception:

Traceback (most recent call last):
File “/opt/seatable/seatable-server-latest/dtable-web/thirdpart/django/core/handlers/”, line 47, in inner
response = get_response(request)
File “/opt/seatable/seatable-server-latest/dtable-web/thirdpart/django/core/handlers/”, line 181, in _get_response
response = wrapped_callback(request, *callback_args, **callback_kwargs)
File “/opt/seatable/seatable-server-latest/dtable-web/thirdpart/django/views/decorators/”, line 54, in wrapped_view
return view_func(*args, **kwargs)
File “/opt/seatable/seatable-server-latest/dtable-web/seahub/saml/”, line 94, in _decorated
return func(request)
File “/opt/seatable/seatable-server-latest/dtable-web/seahub/saml/”, line 190, in acs
File “/opt/seatable/seatable-server-latest/dtable-web/thirdpart/django/db/models/”, line 739, in save
self.save_base(using=using, force_insert=force_insert,
File “/opt/seatable/seatable-server-latest/dtable-web/thirdpart/django/db/models/”, line 776, in save_base
updated = self._save_table(
File “/opt/seatable/seatable-server-latest/dtable-web/thirdpart/django/db/models/”, line 858, in _save_table
updated = self._do_update(base_qs, using, pk_val, values, update_fields,
File “/opt/seatable/seatable-server-latest/dtable-web/thirdpart/django/db/models/”, line 912, in _do_update
return filtered._update(values) > 0
File “/opt/seatable/seatable-server-latest/dtable-web/thirdpart/django/db/models/”, line 802, in _update
return query.get_compiler(self.db).execute_sql(CURSOR)
File “/opt/seatable/seatable-server-latest/dtable-web/thirdpart/django/db/models/sql/”, line 1559, in execute_sql
cursor = super().execute_sql(result_type)
File “/opt/seatable/seatable-server-latest/dtable-web/thirdpart/django/db/models/sql/”, line 1175, in execute_sql
cursor.execute(sql, params)
File “/opt/seatable/seatable-server-latest/dtable-web/thirdpart/django/db/backends/”, line 66, in execute
return self._execute_with_wrappers(sql, params, many=False, executor=self._execute)
File “/opt/seatable/seatable-server-latest/dtable-web/thirdpart/django/db/backends/”, line 75, in _execute_with_wrappers
return executor(sql, params, many, context)
File “/opt/seatable/seatable-server-latest/dtable-web/thirdpart/django/db/backends/”, line 84, in _execute
return self.cursor.execute(sql, params)
File “/opt/seatable/seatable-server-latest/dtable-web/thirdpart/django/db/”, line 90, in exit
raise dj_exc_value.with_traceback(traceback) from exc_value
File “/opt/seatable/seatable-server-latest/dtable-web/thirdpart/django/db/backends/”, line 84, in _execute
return self.cursor.execute(sql, params)
File “/opt/seatable/seatable-server-latest/dtable-web/thirdpart/django/db/backends/mysql/”, line 73, in execute
return self.cursor.execute(query, args)
File “/opt/seatable/seatable-server-latest/dtable-web/thirdpart/MySQLdb/”, line 206, in execute
res = self._query(query)
File “/opt/seatable/seatable-server-latest/dtable-web/thirdpart/MySQLdb/”, line 319, in _query
File “/opt/seatable/seatable-server-latest/dtable-web/thirdpart/MySQLdb/”, line 254, in query
_mysql.connection.query(self, query)
django.db.utils.IntegrityError: (1062, “Duplicate entry ‘’ for key ‘profile_profile_contact_email_0975e4bf_uniq’”)

The SAML configuration was changed in SeaTable 3.5. Please see here: SAML - SeaTable Admin Manual

Also see this prior exchange of yours in this forum: SAML SSO - Error - #8 by cdb

Yes I updated according to the information present in the tutorial, but for a user already registered I have to delete him so that he registers again.

It works for new user.


The link to the admin manual has changed. We published yesterday a new section in the manual “authentication”. There you will find all the necessary information about how authentication works in SeaTable and also how to switch users from one authentication method to another.

Here is the link: Overview - SeaTable Admin Manual

@Vincent, with this information, it should be easy for you to find out why SeaTable denies the login of the user with the error “duplicate entry”.

1 Like

This topic was automatically closed 2 days after the last reply. New replies are no longer allowed.