Forum Discussion

sbeauvais's avatar
sbeauvais
Contributor
12 years ago

[Resolved] request properties not persisting

Hello,

I have some project properties, Username and Password.

Each request in the project uses property expansions to fill in their username and password, i.e.,
Username = ${#Project#Username}
Password = ${#Project#Password}

Unfortunately, every once in a while, I notice that all the requests' Username and Password fields have been cleared! This forces me to re-enter them...

Is this a bug, and if so, how do I work around it?

Am I handling username and password the correct way? Yes, I have several endpoints and switch between them. No, I cannot use environments because our build server uses the regular version of SoapUI (not Pro), where environments are not supported.

I appreciate your support. Thx.

Severin B.
  • SmartBear_Suppo's avatar
    SmartBear_Suppo
    Icon for Alumni rankAlumni
    12 years ago
    Hi,
    What type of request are you using - HTTP/REST/SOAP?
    Can you please provide the steps to reproduce or a sample project?

    Best Regards,
    Prakash
    SmartBear Sweden
  • sbeauvais's avatar
    sbeauvais
    Contributor
    12 years ago
    It's a REST project. As described above, the project has 2 custom properties, Username and Password. The request(s) have, in their properties, property expansions for Username and Password.

    I just duplicated the issue with the attached project, as follows:

    1. Load the project and verify that the request Username and Password are filled in.
    2. Open the WSDL page and select the Service Endpoints tab.
    3. Select an endpoint, click Assign, select "All Requests and TestRequests" and click OK.
    4. Notice that the request Username and Password are now cleared.

    Changing the endpoint directly in the request properties window pane does not clear the properties, so I think globally assigning an endpoint should not either.

    If I am doing this incorrectly, please let me know how to change endpoints for all requests in a project (while still keeping their properties intact).


    SB
  • SmartBear_Suppo's avatar
    SmartBear_Suppo
    Icon for Alumni rankAlumni
    12 years ago
    Hi,

    I was able to reproduce what you are saying; however, the purpose of the Service Endpoints area is to fill out the user name and password along with some other security settings and then assign them to all the requests and\or test requests. Then they will show up in the test requests and\or requests properties in the project.
    Seems like you are doing this the other way around by filling out the request properties for one request first and then trying to assign it using the Service Endpoint which will not work. Please correct me if my assumption is wrong.


    Regards,
    Marcus
    SmartBear Support
  • sbeauvais's avatar
    sbeauvais
    Contributor
    12 years ago
    Hi Marcus,

    Thanks for your help!

    OK, now I understand how assigning endpoints overwrites the Username and Password in the requests. In fact, using endpoints is much cleaner than configuring a lot of property expansions, so I like it

    I had been using custom project properties in every request, but per above, they kept getting overwritten.

    Cheers,
    Severin B.