|
Thanks for your comment
its a little late to response you, forgive me
keep Learning and you never will be out of date...
|
|
|
|
|
has usado recuperacion de password con ADAM, me da un error porque con los controles de ASP.NET de login me pide que ponga la pregunta y respuesta, cosa que no quiero
|
|
|
|
|
Lo siento, pero no he usado esa tecnología, la forma como recupero el password es un sencillo formulario que compara las repuestas a unas preguntas que hago allí, si todas las respuestas concuerdan con la base de datos, termino el formulario enviando un correo con la contraseña al correo asociado al usuario registrado.
Suerte con tu investigación.
PD: Perdon por la demora. He estado un poco ocupada
keep Learning and you never will be out of date...
|
|
|
|
|
I originally assumed this behavior was automatically wired up by the control architechture. This gives me a little to move forward with easily.
Y a propósito.. convengo con el otro personas. Eres muy hermosa. Para nos geeks, es agradable para ver cerebros y belleza en en lo mismo paquete.
Cheers - Brad
|
|
|
|
|
You welcome,
the intention is to make a article that it can serve as guide to understand the operation of this control, you can apply it to the handling of ASP.NET forms that do not use the sqlserver as data base (MySql could be)
Pd: Your last comment (brains and beauty at the same package) is a little bit rough to be a charm.
keep Learning and you never will be out of date...
|
|
|
|
|
hola signora,
i'm not a friend of the ms. login solution, because it will create a own database.
i prefer a own prog. solution, which i can involve in my current oracle-db.
but your documentation is very good. not so boring stuff from others...
cheers,
philipp
|
|
|
|
|
Dont Worry, im ok, i like to confront the people who isnt agree with me, because they make me grown up, but i love the guys who reconoice the peoples effort.
Best regards to you
keep Learning and you never will be out of date...
|
|
|
|
|
Philipp...
You may want to take a look at:
http://www.codeplex.com/AltairisWebProviders
Still this uses SQL but... It's a good example on how to implement a simple(r) version of the membership provider to work with the 2.0 controls. You could likely adapt the provider source to Oracle. Just a thought.
Ciao,
Brad
|
|
|
|
|
Nice example. It was clear and easy to follow... Although, I would have to agree with Adam Tibi.
You may find it in your best interest to invest some time at looking at the membership and role providers for future projects.
I think you would benefit from looking into these providers by taking advantage of the extra funtionality these providers provide. Especially since someone wise once said... "keep Learning and you never will be out of date..."
Later.
|
|
|
|
|
|
these guys are being retarded. this information applies to 2.0. it's kick ass to handle the events from the login interface. nana nanaaaa
beers + e^(X) = beers%
G-
|
|
|
|
|
Hi,
I just wanted to let you know that this is already done with .NET 2.0 membership providers! You don't need to write code to do that, it is already there, so I agree with the previous post of leppie.
To implement the functionality, you only need to do the following:
1 - Configure your SQL Server 2005 for ASP.NET. Or any other data source that you have.
2 - Add code to your Web.config similar to the following code:
<br />
<authentication mode="Forms"><br />
<forms timeout="30" protection="All" loginUrl="~/loginpage.aspx" name=".ASPXAUTH" path="/" slidingExpiration="true" defaultUrl="default.aspx" cookieless="UseDeviceProfile" enableCrossAppRedirects="false"/><br />
</authentication><br />
<membership userIsOnlineTimeWindow="20"><br />
<providers><br />
<clear/><br />
<add applicationName="/Default" name="AspNetSqlMembershipProvider" connectionStringName="Default" type="System.Web.Security.SqlMembershipProvider" enablePasswordRetrieval="false" enablePasswordReset="true" requiresQuestionAndAnswer="false" maxInvalidPasswordAttempts="7" passwordFormat="Hashed"/><br />
</providers><br />
</membership><br />
<roleManager enabled="true"><br />
<providers><br />
<clear/><br />
<add applicationName="/Default" name="AspNetSqlRoleProvider" connectionStringName="Default" type="System.Web.Security.SqlRoleProvider"/><br />
</providers><br />
</roleManager><br />
<authorization><br />
<allow roles="AuthUsers"/><br />
<deny users="?"/><br />
</authorization><br />
3 - Drop a login control on the login page.
And you are done!
I am sorry to say that the article is misleading.
Regards,
Adam Tibi
-- modified at 4:48 Thursday 7th December, 2006
-- modified at 4:48 Thursday 7th December, 2006
Make it simple, as simple as possible, but not simpler.
|
|
|
|
|
A misleading? , Mr Adam Tibi you know that in systems enviroment the others departments like financier or human resources do not have idea how long a project comsume time in order to reach an good end. We dont even know.
The human resources on my new job asking me for at 2.0 solution to login exist users, So, i based this solution over my 1.1 development solution. because they want a Just in time solution, right know i dont have free time to read about Memberships, so the fastest way is based a solution over something that you already know.
Good for you, If you know how to implement menberships providers, but what happened with the not experimented developers like me?..
The only that i want is to show my transition between the login PAGE in 1.1 net Version using a 2.0 Net login CONTROL.
Best regards
keep Learning and you never will be out of date...
|
|
|
|
|
A misleading, Miss Britney S. Morales, as in that I had to look through the code to make sure that I am not missing any feature of .NET 2.0 then I realised that the author didn't take into account any additions to the second version of ASP.NET. For an unexperienced developer, he/she might follow your article and waste time to reinvent the wheel in addition to introducing some bugs like the SQL injuction security bug.
How weired that you didn't have time to read about the membership subject, on the other hand, you had time to write the article!
Knowing how to use membership providers doesn't require an experienced user, but extending it does and normally you won't need to do that.
A positive thing to mention about the article is that it is clear, well explained with nice looking figures. It looks that you have invested time on it to deliver a better quality job.
Regards,
Adam Tibi
Make it simple, as simple as possible, but not simpler.
|
|
|
|
|
Wow, despacio! Perdon mi español, soy de UUEE. Bueno, Adam es correcto y no. Puedes usar el Membership porque todo es incluido en el .NET Framework. Pero, si ya tienes un database, es mas dificil y necesitas hacer tu misma codigo de un MembershipProvider. Estoy haciendo esto en mi proyecto.
Sin embargo, todavia necesito usar el evento "Authenticate" porque no hay forma que conseguir un exception del Membership Provider. Yo quiro mostrar mensajes mas amiable a los usarios. Entonces, necesito hacer como hiciste.
|
|
|
|
|
u can use
if (Logeo.RememberMeSet )
instead of
CheckBox chBox = (CheckBox)Logeo.FindControl("RememberMe");<br />
if (chBox.Checked)<br />
|
|
|
|
|
all images in the article are so cool!!
|
|
|
|
|
AACCoder im only used the login control, im working now in how to implement the others controls
keep Learning and you never will be out of date...
|
|
|
|
|
Nice example the code is not secure but the objetive save the user id is OK.
so far so good...
|
|
|
|
|
Roling your own login system might be fun, but it stops there! Have a look at the builtin SQL User/Role/Profile provider. That plugs straight into the login controls, and does a fine job of covering any holes. If however you want to use your own system, you can simply inherit from the one of the provider base classes and shape your own backend (easier said than done though!).
Cheers
|
|
|
|
|
Few questions if you do not mind:
1. Are you using ASP.NET 2.0 built-in login control? Not clear.
2. ExecuteReader() may return more than 1 row. How would you handle such case?
3. You do not close a connection in case of an error.
4. How about "Forgot password?" scenario?
|
|
|
|
|
1. The sample images look like 2005
2. A simple unique index on username takes care of that scenario.
3. Maybe wrap the connection in a using
4. Asp.Net 2.0 password recovery control?
|
|
|
|
|
1. Yes its a Asp.Net 2.0
2. Good question, i must to evaluate if to use the sentence
string cod_user = comandoSql.ExecuteScalar().ToString();
3. Yes, thats a bad luck , i will modify the code. thanks
4. Edboe is right, Asp.Net 2.0 password recovery control. How Implement it, im working in that...
keep Learning and you never will be out of date...
|
|
|
|
|
sorry,i have a question.
when your database is not mssql ,how we can use the login control? if you had made it out ?
happy to see your reply.
|
|
|
|
|
I didnt work over another database engine than not to be SQL.
But i have some ideas.
Normally you connect to another database (no SQL) using DSN (data source name) with a ODBC control, so, the only thing who change in the example code will be the database connection query, and all the database controls will not sqldatareader... sqlcommand..., they are odbcdatareader, odbccommand.. etc.
keep Learning and you never will be out of date...
|
|
|
|