<span name="Tornóci László" class="gD">I'm agree with the solution proposed by Tornóci László</span> <span class="go"></span><br><br>Other option is to allow the user to change his password without knowing his old password, maybe using a "reset password based on mail functionality".<br>
(Only users that plan to use a non-web based interface will be required to do that)<br><br><br><br><div class="gmail_quote">2013/6/26 Tornóci László <span dir="ltr"><<a href="mailto:tornoci.laszlo@med.semmelweis-univ.hu" target="_blank">tornoci.laszlo@med.semmelweis-univ.hu</a>></span><br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div class="im">On 06/26/2013 12:16 PM, alen vodopijevec wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
Dear OwnCloud-ers,<br>
<br>
we have a test implementation of Owncloud instance at our institution<br>
(since ver. 4.5.0). So far a dozen of our users happily share their<br>
files and collaborate. "user_saml" is working fine with OC 5.0.7.<br>
<br>
Current system specification:<br>
--<br>
1. Owncloud ver. 5.0.7 on Debian GNU Linux system (simplesaml sP)<br>
2. A few standard plugins<br>
3. user_saml plugin (with couple of adjustments regarding user<br>
filtering) for authentication through our national authentication and<br>
authorization system AAI@EduHr (<a href="http://www.aaiedu.hr" target="_blank">http://www.aaiedu.hr</a>)<br>
--<br>
<br>
I'm experimenting with sync client (1.3.0) but there is catch. When user<br>
authenticates (user_saml) for the first time he/she gets a new record on<br>
"oc_users" table with random password -> OK.. simplesamlphp manages user<br>
login, so system password is not used for web logins.<br>
<br>
<br>
PROBLEM:<br>
Users cannot use sync clients because they don't know their random<br>
system password and they cannot even change it because of the same<br>
issue.. Admin user can change other user passwords (after applying patch<br>
<a href="https://github.com/owncloud/core/commit/563f343291fb5d0292c66cb761a053557bfdae47" target="_blank">https://github.com/owncloud/<u></u>core/commit/<u></u>563f343291fb5d0292c66cb761a053<u></u>557bfdae47</a>)<br>
.. thats ok but it's not the real solution.<br>
</blockquote>
<br>
<br></div>
I think there is a simple solution, if you have access to the LDAP that is the backend to the identity provider service. Simply untick the "Autocreate user after SAML login" and set up LDAP auth too. The first prevents the creation of a record in oc_users. The second provides you auth for webdav services. This setup works for me quite well.<br>
<br>
Yours: Laszlo<div class="HOEnZb"><div class="h5"><br>
______________________________<u></u>_________________<br>
Owncloud mailing list<br>
<a href="mailto:Owncloud@kde.org" target="_blank">Owncloud@kde.org</a><br>
<a href="https://mail.kde.org/mailman/listinfo/owncloud" target="_blank">https://mail.kde.org/mailman/<u></u>listinfo/owncloud</a><br>
</div></div></blockquote></div><br><br clear="all"><br>-- <br>Sixto Pablo Martín García<br>Ingeniero Informático<br><div>Yaco Sistemas SL</div><div>Teléfono +34 954 50 00 57<br>C/Rioja 5-1ª Planta<br></div><div>41001 Sevilla</div>